Triple
T27391848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 5R/23L |
E691556
|
entity |
| Predicate | identifiedByFAA |
P156057
|
FINISHED |
| Object | 5R/23L |
—
|
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: 5R/23L | Statement: [Runway 5R/23L, identifiedByFAA, 5R/23L]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiedByFAA Context triple: [Runway 5R/23L, identifiedByFAA, 5R/23L]
-
A.
isInFAARegistry
Indicates that an aircraft or related entity is officially recorded and recognized in the Federal Aviation Administration’s (FAA) registry.
-
B.
has FAA LID
chosen
Indicates that an entity (typically an airport or aviation facility) is assigned a specific FAA Location Identifier code.
-
C.
identifiedInATCSystemsBy
Indicates that an entity is recognized or labeled within Air Traffic Control (ATC) systems by a specific identifier or reference.
-
D.
aircraftRegistration
Indicates that an aircraft is assigned a specific official registration identifier or code.
-
E.
FAAclassification
Indicates the type or category assigned to something under the Federal Aviation Administration’s (FAA) classification system.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 12:26 p.m.