Triple
T6429091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Carlos de Bariloche Airport |
E128132
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | SAZS |
E535159
|
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: SAZS | Statement: [San Carlos de Bariloche Airport, ICAOcode, SAZS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SAZS Context triple: [San Carlos de Bariloche Airport, ICAOcode, SAZS]
-
A.
SAZS
chosen
SAZS is the ICAO airport code for San Carlos de Bariloche Airport, a major gateway to the Patagonia region of Argentina.
-
B.
SAEZ
SAEZ is the ICAO airport code for Ministro Pistarini International Airport, the main international gateway serving Buenos Aires, Argentina.
-
C.
ZAZ
ZAZ is the IATA airport code for Zaragoza Airport, a major civilian and military airfield serving the city of Zaragoza in northeastern Spain.
-
D.
ASDZ
ASDZ is the station code used to identify Amsterdam Zuid railway station in the Netherlands.
-
E.
ZS
ZS is the vehicle registration code assigned to cars registered in the Polish city of Szczecin.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06923b12081908a09543450b88c24 |
completed | March 22, 2026, 10:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c640e678608190b5a1dcd1076bc1f2 |
completed | March 27, 2026, 8:33 a.m. |
Created at: March 22, 2026, 4:44 p.m.