Triple
T8102549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cologne Bonn Airport |
E189148
|
entity |
| Predicate | hasCityCode |
P6089
|
FINISHED |
| Object | CGN |
E711564
|
NE 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: CGN | Statement: [Cologne Bonn Airport, hasCityCode, CGN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CGN Context triple: [Cologne Bonn Airport, hasCityCode, CGN]
-
A.
CGN
CGN is a Swiss company that operates passenger ferry and cruise services on Lake Geneva.
-
B.
CGN
chosen
CGN is the IATA airport code for Cologne Bonn Airport, a major international airport serving the Cologne and Bonn region in western Germany.
-
C.
CN-GS
CN-GS is the ISO 3166-2 code representing Gansu Province, a landlocked region in north-central China known for its role along the historic Silk Road.
-
D.
KGN
KGN is the standard three-letter abbreviation used for the Kingston Frontenacs, a major junior ice hockey team in the Ontario Hockey League.
-
E.
CGR
CGR is the IATA airport code for Campo Grande International Airport in Campo Grande, Brazil.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82b886d88190a9cba0d5a4a27521 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42bd91408190880293dfdce8bef7 |
completed | March 31, 2026, 3:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc941075588190a9b12e2f873ba2a5 |
completed | April 1, 2026, 3:42 a.m. |
Created at: March 30, 2026, 5:31 p.m.