Triple
T3459444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAR |
E72987
|
entity |
| Predicate | IATACodeType |
P418
|
FINISHED |
| Object | city code |
—
|
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: city code | Statement: [PAR, IATACodeType, city code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IATACodeType Context triple: [PAR, IATACodeType, city code]
-
A.
hasIATAcode
Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
-
B.
IATAcode
chosen
Indicates the three-letter IATA airport or airline code assigned to the entity.
-
C.
isocodeCategory
Indicates that an entity is classified under a specific ISO code category or grouping.
-
D.
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.
-
E.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae4c18881908b48d16e46f78209 |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.