Triple
T4991301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 01R/19L |
E112134
|
entity |
| Predicate | hasLeftSideDesignator |
P54806
|
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 01R/19L, hasLeftSideDesignator, L]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeftSideDesignator Context triple: [Runway 01R/19L, hasLeftSideDesignator, L]
-
A.
hasPortionDesignatedAs
Indicates that one entity has a specific part or segment that is explicitly identified or designated as another entity.
-
B.
hasEquationSide
Indicates a relationship where a particular expression or term belongs to a specific side (e.g., left or right) of an equation.
-
C.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
-
D.
hasRunwayDesignationSide
chosen
Indicates that a runway designation is associated with a specific side or direction of the runway (e.g., left, right, or center).
-
E.
hasLeftPillarCandidate
Indicates that an entity has a potential or designated candidate to serve as its left pillar in a structural or relational configuration.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.