Triple
T10909853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FVHA |
E257666
|
entity |
| Predicate | hasIcaoPrefix |
P49384
|
FINISHED |
| Object | FV |
—
|
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: FV | Statement: [FVHA, hasIcaoPrefix, FV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIcaoPrefix Context triple: [FVHA, hasIcaoPrefix, FV]
-
A.
hasICAOComplement
Indicates that one entity serves as an ICAO-standard complement or additional code/information corresponding to another entity’s primary ICAO designation.
-
B.
hasAirportCodePrefix
chosen
Indicates that an airport’s code begins with a specified sequence of characters.
-
C.
ICAOTypeDesignator
Indicates the standardized aircraft type code assigned by ICAO that specifies the model or family of an aircraft used in aviation operations and documentation.
-
D.
hasIATAcode
Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77068e5488190bbc881ebf51d6b2e |
completed | April 9, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.