Triple
T3999632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 07L/25R |
E87182
|
entity |
| Predicate | isNumberedByMagneticHeading |
P37553
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [Runway 07L/25R, isNumberedByMagneticHeading, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNumberedByMagneticHeading Context triple: [Runway 07L/25R, isNumberedByMagneticHeading, true]
-
A.
isNumberedBy
chosen
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
B.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
C.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
D.
magneticFieldStrength
Indicates the intensity or magnitude of a magnetic field associated with an entity or at a specific location.
-
E.
hasBearingPattern
Indicates a relationship where an object or system exhibits or is characterized by a specific bearing arrangement or configuration pattern.
- F. None of above.
Provenance (3 batches)
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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa8579288190940487ad07e38de0 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8f89f2881909b0965419d15d46c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.