Can Rules of Inferences Resolve Coordination Ambiguity in Natural Language Requirements Specification
Bibliographic record
Abstract
Coordination ambiguity is the ambiguity that occurs from the use of coordinators such as and and or. The first author’s previous work tried to resolve coordination ambiguity in natural language (NL) requirements specifications (RSs) by using language patterns derived from rules of logic (RLs). However, a reevaluation of the language patterns show that RLs cannot fully resolve coordination ambiguity in a RS because the coordinators are not always truth functional, due to incompatible interpretations that a human ascribes to the ambiguous RS. Furthermore, human perceptions in the interpretation of the coordinators in a RS vary incredibly widely. The implications of this observation on requirements elicitation are discussed. 1
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.036 | 0.146 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.002 | 0.007 |
| Scholarly communication | 0.012 | 0.022 |
| Open science | 0.003 | 0.004 |
| Research integrity | 0.005 | 0.003 |
| Insufficient payload (model declined to judge) | 0.003 | 0.002 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".