Triple
T12313208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SBSP |
E293533
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | CGH |
E293532
|
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: CGH | Statement: [SBSP, IATAcode, CGH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CGH Context triple: [SBSP, IATAcode, CGH]
-
A.
CGH
chosen
CGH is the IATA airport code for Congonhas–São Paulo Airport, a major domestic airport serving the city of São Paulo, Brazil.
-
B.
CGR
CGR is the IATA airport code for Campo Grande International Airport in Campo Grande, Brazil.
-
C.
GCH
GCH is the vehicle registration code assigned to a specific district within Poland’s Pomeranian Voivodeship.
-
D.
CGCT
CGCT is the standard abbreviation for the French Code général des collectivités territoriales, the legal framework governing the organization and functioning of local authorities in France.
-
E.
CGF
CGF is the abbreviation for the Commonwealth Games Federation, the international organization responsible for overseeing and managing the Commonwealth Games and related sporting events.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f03d3c88190baedffb83465bff8 |
completed | April 10, 2026, 6:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f62a9d50b081908f0bdb7a2ca2832a |
completed | May 2, 2026, 4:47 p.m. |
Created at: April 8, 2026, 9:53 p.m.