Triple
T14615412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galeão Air Base |
E343071
|
entity |
| Predicate | hasIcaoCode |
P419
|
FINISHED |
| Object | SBGL |
E209310
|
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: SBGL | Statement: [Galeão Air Base, hasIcaoCode, SBGL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SBGL Context triple: [Galeão Air Base, hasIcaoCode, SBGL]
-
A.
SBGL
chosen
SBGL is the ICAO airport code for Rio de Janeiro–Galeão International Airport, a major international gateway serving Rio de Janeiro, Brazil.
-
B.
SGL
SGL is the station code for Singleton railway station, a train stop serving the locality of Singleton.
-
C.
SBG
SBG is the abbreviation of the Société Biblique de Genève, a Geneva-based Bible society dedicated to translating, publishing, and distributing the Bible.
-
D.
SBGR
SBGR is the ICAO airport code for São Paulo–Guarulhos International Airport, the main international gateway serving São Paulo, Brazil.
-
E.
SBGI
SBGI is the stock ticker symbol for Sinclair Broadcast Group, a major American telecommunications company and television station owner.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb45264988190a1df13e8b54a85bd |
completed | April 14, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fda922f29c8190af98a8241d86f7cd |
completed | May 8, 2026, 9:13 a.m. |
Created at: April 10, 2026, 1:25 a.m.