Triple
T33051466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Hurn |
E845733
|
entity |
| Predicate | hasICAOCodeSuccessor |
P45327
|
FINISHED |
| Object | EGHH |
—
|
NE NERFINISHED |
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: EGHH | Statement: [RAF Hurn, hasICAOCodeSuccessor, EGHH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasICAOCodeSuccessor Context triple: [RAF Hurn, hasICAOCodeSuccessor, EGHH]
-
A.
hasIATASuccessor
Indicates that one entity is the airport or airline that officially succeeds another according to IATA designation or coding.
-
B.
previousICAOcode
Indicates that one entity was the former ICAO (International Civil Aviation Organization) code previously assigned to the other entity.
-
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.
hasICAOComplement
Indicates that one entity serves as an ICAO-standard complement or additional code/information corresponding to another entity’s primary ICAO designation.
-
E.
hasIATAcode
Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.