Triple
T17939947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirupati Airport |
E448559
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | TIR |
—
|
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: TIR | Statement: [Tirupati Airport, IATA code, TIR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TIR Context triple: [Tirupati Airport, IATA code, TIR]
-
A.
TIR
chosen
TIR is the IATA airport code for Tirupati Airport, which serves the pilgrimage city of Tirupati in Andhra Pradesh, India.
-
B.
TIAR
TIAR is a 1947 mutual defense pact among many countries of the Americas that commits them to collective security in the event of an armed attack on any member state.
-
C.
Tiel
Tiel is a historic Dutch city situated along the River Waal, known for its fruit cultivation and role as a regional trade center in the province of Gelderland.
-
D.
TIJ
TIJ is the IATA airport code for Tijuana International Airport in Tijuana, Mexico.
-
E.
TIRS
TIRS is a thermal infrared imaging instrument used on satellites like Landsat 8 to measure Earth's surface temperature and support environmental monitoring.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad9533688190bff773c183ed8505 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 10:21 a.m.