Triple
T19839516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Antonio International Airport |
E476687
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | KSAT |
—
|
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: KSAT | Statement: [San Antonio International Airport, ICAOCode, KSAT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KSAT Context triple: [San Antonio International Airport, ICAOCode, KSAT]
-
A.
KSAT
chosen
KSAT is the ICAO airport code for San Antonio International Airport, a major commercial airport serving the San Antonio, Texas area.
-
B.
KSAD
KSAD is the commonly used abbreviation for the position of Chief of Staff of the Indonesian Army, the highest-ranking officer responsible for leading and managing Indonesia’s land forces.
-
C.
KTS
KTS is the station code for Kalutara South railway station on Sri Lanka’s coastal railway line.
-
D.
KS
KS is the standard two-letter postal abbreviation for the U.S. state of Kansas.
-
E.
KS
KS is the vehicle registration code used on license plates for the German city of Kassel.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65804be608190b49e110c3bf381bc |
completed | April 20, 2026, 4:44 p.m. |
Created at: April 10, 2026, 1:50 p.m.