Triple
T22678697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPW |
E560418
|
entity |
| Predicate | hasIATAStyle |
P149212
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [CPW, hasIATAStyle, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIATAStyle Context triple: [CPW, hasIATAStyle, no]
-
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.
hasIATAFlightNumber
Indicates that an entity (typically a flight) is associated with a specific IATA-designated flight number.
-
C.
IATACompliance
Indicates that an entity adheres to the standards, regulations, or requirements set by the International Air Transport Association (IATA).
-
D.
hasIATAOverlap
Indicates that two entities share at least one overlapping or identical IATA code designation.
-
E.
hasIcaoCodeFormat
Indicates that an entity’s ICAO code conforms to a specified structural or formatting pattern.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1785e4e7481909f1ebd6d8dbd6585 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:11 p.m.