Triple
T17970208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Dalcross |
E449315
|
entity |
| Predicate | IATACodeSuccessor |
P45327
|
FINISHED |
| Object | INV |
—
|
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: INV | Statement: [RAF Dalcross, IATACodeSuccessor, INV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IATACodeSuccessor Context triple: [RAF Dalcross, IATACodeSuccessor, INV]
-
A.
hasIATASuccessor
Indicates that one entity is the airport or airline that officially succeeds another according to IATA designation or coding.
-
B.
successorCode
Indicates that one code directly follows and replaces another code in a defined sequence or versioning scheme.
-
C.
successorCodeForSameAirport
chosen
Indicates that one code is the direct replacement or follow-up code for the same airport, reflecting a change while the underlying airport remains the same.
-
D.
hasICAOSuccessorCode
Indicates that one ICAO airport code has been replaced or superseded by another ICAO airport code.
-
E.
previousICAOcode
Indicates that one entity was the former ICAO (International Civil Aviation Organization) code previously assigned to the other 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b1fa67c48190936f20cea45e4599 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.