Triple
T11891309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trinidad and Tobago dollar |
E282919
|
entity |
| Predicate | ISO4217AlphaCode |
P12372
|
FINISHED |
| Object | TTD |
E282919
|
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: TTD | Statement: [Trinidad and Tobago dollar, ISO4217AlphaCode, TTD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TTD Context triple: [Trinidad and Tobago dollar, ISO4217AlphaCode, TTD]
-
A.
TTD
chosen
TTD is the official currency code for the Trinidad and Tobago dollar, the national currency of Trinidad and Tobago.
-
B.
TTD
TTD is the governing body that manages the Tirumala Venkateswara Temple and associated institutions in Tirupati, India.
-
C.
TTD
TTD is the three-letter IATA airport code assigned to Troutdale Airport in Troutdale, Oregon, near Portland.
-
D.
TTA
TTA is the IATA airport code for Raleigh Executive Jetport, a general aviation airport serving the Raleigh, North Carolina area.
-
E.
TTA
TTA (Telecommunications Technology Association) is South Korea’s primary standards organization for information and communication technologies, contributing to global telecom standards development.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a3f7548190adfb567f060a175a |
completed | April 10, 2026, 10:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f417f7f268819091bdb72394506808 |
completed | May 1, 2026, 3:03 a.m. |
Created at: April 8, 2026, 9:44 p.m.