Triple
T8816455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santos Dumont Airport |
E209788
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | SBRJ |
E209789
|
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: SBRJ | Statement: [Santos Dumont Airport, ICAOcode, SBRJ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SBRJ Context triple: [Santos Dumont Airport, ICAOcode, SBRJ]
-
A.
SBRJ
chosen
SBRJ is the ICAO airport code for Santos Dumont Airport, a major domestic airport located near downtown Rio de Janeiro, Brazil.
-
B.
SBRF
SBRF is the ICAO airport code for Recife/Guararapes–Gilberto Freyre International Airport, a major air transport hub in northeastern Brazil.
-
C.
SBBR
SBBR is the ICAO airport code for Brasília International Airport, the main air gateway serving Brazil’s capital city.
-
D.
SRB
SRB is the three-letter ISO 3166-1 alpha-3 country code assigned to Serbia.
-
E.
SRB
The SRB is the European Union agency responsible for managing the orderly resolution of failing banks within the Banking Union to protect financial stability and taxpayers.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc600bd8a88190ad891a96201d796b |
completed | April 1, 2026, midnight |
| NED1 | Entity disambiguation (via context triple) | batch_69cf6fb898388190b96242ff41599250 |
completed | April 3, 2026, 7:43 a.m. |
Created at: March 30, 2026, 6:46 p.m.