Triple
T38417190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annex 14 — Aerodromes |
E903130
|
entity |
| Predicate | includesRequirementFor |
—
|
GENERATED |
| Object | runway design |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRequirementFor Context triple: [Annex 14 — Aerodromes, includesRequirementFor, runway design]
-
A.
mayIncludeRequirement
Indicates that something can optionally contain or encompass a particular requirement as part of its definition or structure.
-
B.
containsCoreRequirement
Indicates that one entity includes or encompasses another entity that is designated as a core or essential requirement.
-
C.
componentRequirement
Indicates that one component depends on or necessitates the presence or use of another component to function or be considered complete.
-
D.
establishedRequirement
chosen
Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
-
E.
requirementType
Indicates the specific category or classification of a given requirement within a broader requirements framework or system.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.