Triple
T23322444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 13R/31L |
E591187
|
entity |
| Predicate | hasLeftSideDesignation |
P151868
|
FINISHED |
| Object | 31L |
—
|
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: 31L | Statement: [Runway 13R/31L, hasLeftSideDesignation, 31L]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeftSideDesignation Context triple: [Runway 13R/31L, hasLeftSideDesignation, 31L]
-
A.
sideDesignation
Indicates how an entity is classified or labeled with respect to a particular side, position, or alignment within a relationship or context.
-
B.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
C.
hasKVDesignation
Indicates that an entity has been assigned a specific KV (classification or designation) label or code.
-
D.
hasPortionDesignatedAs
Indicates that one entity has a specific part or segment that is explicitly identified or designated as another entity.
-
E.
hasPadDesignation
Indicates that an entity is assigned or associated with a specific pad identifier or designation.
- F. None of above. chosen
Provenance (4 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1978672148190bb90804361bb896b |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:07 p.m.