Triple
T11891308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TTD |
E282919
|
entity |
| Predicate | hasISO4217AlphaCode |
P34151
|
FINISHED |
| Object | TTD |
—
|
LITERAL 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: [TTD, hasISO4217AlphaCode, TTD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISO4217AlphaCode Context triple: [TTD, hasISO4217AlphaCode, TTD]
-
A.
hasISO4217Status
Indicates the classification or status of a currency according to the ISO 4217 standard.
-
B.
ISO 4217 code
Indicates the standardized three-letter currency code assigned to a monetary unit according to the ISO 4217 international standard.
-
C.
formerISO4217Code
Indicates that an entity was previously assigned a particular ISO 4217 currency code that is no longer in current use for it.
-
D.
hasISO4217ThreeLetterCode
chosen
Indicates that an entity is associated with a specific three-letter currency code defined by the ISO 4217 standard.
-
E.
ISO4217CodeOfCurrency
Indicates that one entity is the ISO 4217 currency code that formally designates the other entity as a specific currency.
- F. None of above.
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. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.