Triple
T26840924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBE |
E675772
|
entity |
| Predicate | hasIATAConfusionWith |
P152924
|
FINISHED |
| Object | CJB |
—
|
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: CJB | Statement: [CBE, hasIATAConfusionWith, CJB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIATAConfusionWith Context triple: [CBE, hasIATAConfusionWith, CJB]
-
A.
IATAConfusionWith
chosen
Indicates that two entities are often mistaken for each other due to having similar or easily confused IATA airport codes.
-
B.
hasIATAcode
Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
-
C.
hasIATAOverlap
Indicates that two entities share at least one overlapping or identical IATA code designation.
-
D.
hasIATAFunction
Indicates that an entity has a specific role, status, or function as defined by the International Air Transport Association (IATA).
-
E.
notIATA
Indicates that an entity does not have, or is not associated with, an 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61b46b20481908ee866c36e4cdd7b |
completed | May 2, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:08 a.m.