Triple
T12665143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 06R/24L |
E302530
|
entity |
| Predicate | runwayEndDesignation |
P54806
|
FINISHED |
| Object | 06R |
—
|
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: 06R | Statement: [Runway 06R/24L, runwayEndDesignation, 06R]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayEndDesignation Context triple: [Runway 06R/24L, runwayEndDesignation, 06R]
-
A.
runwayEnd
Indicates that one entity represents the end point or terminus of a runway associated with the other entity.
-
B.
runwayEndHeading
Indicates the directional heading or bearing associated with the end of a runway, typically expressed in degrees relative to north.
-
C.
hasRunwayDesignationSide
chosen
Indicates that a runway designation is associated with a specific side or direction of the runway (e.g., left, right, or center).
-
D.
runwayCharacteristic
Indicates a relationship where specific attributes or features are associated with a runway.
-
E.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617e030881908444743b8a7e0d75 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:19 p.m.