Triple
T33962567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 03/21 |
E870756
|
entity |
| Predicate | airportIdentifier |
P179365
|
FINISHED |
| Object | ROW |
—
|
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: ROW | Statement: [Runway 03/21, airportIdentifier, ROW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportIdentifier Context triple: [Runway 03/21, airportIdentifier, ROW]
-
A.
airportCodeFAA
Indicates that an airport is identified by a specific FAA (Federal Aviation Administration) airport code.
-
B.
airportRecognition
Indicates that an entity formally acknowledges, identifies, or designates another entity as an airport.
-
C.
airportCodeContext
Indicates that an airport code is being used or interpreted within a specific contextual framework (such as a region, system, or standard) that defines its meaning.
-
D.
airportIATAAssociated
Indicates that an airport is associated with a specific IATA (International Air Transport Association) code.
-
E.
airportUse
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f720cc1bfc8190a16118e3af8e9316 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71fb0172c81908f23e95ff16b0dec |
completed | May 3, 2026, 10:13 a.m. |
Created at: May 1, 2026, 1:50 a.m.