Triple
T8037271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway A 16L/34R |
E187137
|
entity |
| Predicate | hasSideDesignation |
P62081
|
FINISHED |
| Object | left for direction 16 |
—
|
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: left for direction 16 | Statement: [Runway A 16L/34R, hasSideDesignation, left for direction 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSideDesignation Context triple: [Runway A 16L/34R, hasSideDesignation, left for direction 16]
-
A.
sideDesignation
chosen
Indicates how an entity is classified or labeled with respect to a particular side, position, or alignment within a relationship or context.
-
B.
hasInternalDesignationFor
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
-
C.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
D.
hasDesignationBy
Indicates that one entity has been formally assigned or labeled with a specific designation by another entity.
-
E.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
- 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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f188e1c8190b92760c91d31f2df |
completed | March 31, 2026, 3:27 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:23 p.m.