Triple
T17849701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 08L/26R |
E445763
|
entity |
| Predicate | leftRightDesignation |
P62081
|
FINISHED |
| Object | L for 08 direction |
—
|
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: L for 08 direction | Statement: [Runway 08L/26R, leftRightDesignation, L for 08 direction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leftRightDesignation Context triple: [Runway 08L/26R, leftRightDesignation, L for 08 direction]
-
A.
leftPosition
Indicates that one entity is located to the left side of another entity in space or ordering.
-
B.
leftFeature
Indicates that one entity functions as a feature or characteristic located on the left side of another entity.
-
C.
leftLandmark
Indicates that one entity is positioned to the left side of another entity, serving as a spatial reference point or landmark.
-
D.
directionalDesignation
Indicates a relationship where one entity is assigned or labeled with a specific directional orientation relative to another entity or reference frame.
-
E.
sideDesignation
chosen
Indicates how an entity is classified or labeled with respect to a particular side, position, or alignment within a relationship or context.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48ffd7e2c81909a42cc7ab64e7db9 |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.