Triple
T2406772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thai Airways International |
E50293
|
entity |
| Predicate | ICAOcode |
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 Airways International, ICAOcode, THA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: THA Context triple: [Thai Airways International, ICAOcode, THA]
-
A.
THA
chosen
THA is the three-letter ISO 3166-1 alpha-3 country code representing Thailand.
-
B.
TKR
TKR is the abbreviated name of the People's Security Army, a military or paramilitary organization associated with internal security and defense.
-
C.
TPA
TPA is the three-letter IATA airport code for Tampa International Airport, a major commercial airport serving the Tampa Bay area in Florida, USA.
-
D.
TPA
TPA is an abbreviation commonly used for a Tri-Party Agreement, a legal contract involving three separate parties that defines their respective rights and obligations.
-
E.
TH
TH is the two-letter ISO 3166-1 alpha-2 country code assigned to Thailand for international standardization and identification.
- 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_69a88b0339a88190a1207333cd271cc9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc8fcd3008190b27325e6829ae7ce |
completed | March 7, 2026, 6:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aeb3eba9d08190a2c63e590e08b4df |
completed | March 9, 2026, 11:50 a.m. |
Created at: March 4, 2026, 7:58 p.m.