Triple
T28801001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 11L/29R |
E727232
|
entity |
| Predicate | leftOrRightDesignator |
P151868
|
FINISHED |
| Object | L |
—
|
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 | Statement: [Runway 11L/29R, leftOrRightDesignator, L]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leftOrRightDesignator Context triple: [Runway 11L/29R, leftOrRightDesignator, L]
-
A.
hasLeftSideDesignation
chosen
Indicates that a specific designation, label, or marker is assigned to the left side of an object, structure, or spatial arrangement.
-
B.
leftPosition
Indicates that one entity is located to the left side of another entity in space or ordering.
-
C.
leftLandmark
Indicates that one entity is positioned to the left side of another entity, serving as a spatial reference point or landmark.
-
D.
leftFeature
Indicates that one entity functions as a feature or characteristic located on the left side of another entity.
-
E.
directionalDesignation
Indicates a relationship where one entity is assigned or labeled with a specific directional orientation relative to another entity or reference frame.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:27 a.m.