Triple
T23259225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pampulha Airport |
E581957
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | SBBH |
—
|
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: SBBH | Statement: [Pampulha Airport, ICAOCode, SBBH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SBBH Context triple: [Pampulha Airport, ICAOCode, SBBH]
-
A.
SBBH
chosen
SBBH is the ICAO airport code for Belo Horizonte/Pampulha – Carlos Drummond de Andrade Airport, a domestic airport serving the city of Belo Horizonte in Brazil.
-
B.
SBBE
SBBE is the ICAO airport code for Belém Air Base, a military airfield located in Belém, Brazil.
-
C.
SBH
SBH is the IATA airport code for Gustaf III Airport, the small Caribbean airfield serving the island of Saint Barthélemy.
-
D.
CBBH
CBBH is the central monetary authority of Bosnia and Herzegovina, responsible for issuing the national currency and maintaining the country’s monetary and financial stability.
-
E.
bhb
bhb is the ISO 639-3 language code for Bhili, an Indo-Aryan language spoken primarily by the Bhil people in western and central India.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f194c7ec148190b01fd215a0c1daa1 |
completed | April 29, 2026, 5:19 a.m. |
Created at: April 17, 2026, 4:11 p.m.