Triple
T11095080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | THAI |
E262356
|
entity |
| Predicate | associatedWithICAOCode |
P419
|
FINISHED |
| Object | THA |
E31688
|
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: THA | Statement: [THAI, associatedWithICAOCode, THA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: THA Context triple: [THAI, associatedWithICAOCode, THA]
-
A.
THA
chosen
THA is the three-letter ISO 3166-1 alpha-3 country code representing Thailand.
-
B.
THA
THA is the National Rail station code for Thatcham railway station in Berkshire, England.
-
C.
TKA
TKA is a regional vehicle registration code used on license plates for cars registered in the Kazimierza Wielka area of Poland.
-
D.
TKR
TKR is the abbreviated name of the People's Security Army, a military or paramilitary organization associated with internal security and defense.
-
E.
TJM
TJM is the IATA airport code for Roshchino International Airport serving Tyumen in western Siberia, Russia.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a0783e88190aae3d461730c2d70 |
completed | April 9, 2026, 12:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3e7e0c7e4819098e690ffebbd8e61 |
completed | April 18, 2026, 8:21 p.m. |
Created at: April 8, 2026, 9:27 p.m.