Triple
T668536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITL |
E12919
|
entity |
| Predicate | cashEuroIntroduction |
P18112
|
FINISHED |
| Object | 2002-01-01 |
—
|
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: 2002-01-01 | Statement: [ITL, cashEuroIntroduction, 2002-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cashEuroIntroduction Context triple: [ITL, cashEuroIntroduction, 2002-01-01]
-
A.
currency
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
-
B.
currencyInitiative
Indicates an initiative, program, or action specifically related to the development, regulation, promotion, or reform of a currency or monetary system.
-
C.
currencyContext
Indicates that a particular monetary value or transaction is expressed, interpreted, or valid within a specified currency framework or setting.
-
D.
currencyModel
Indicates that something uses, is based on, or conforms to a particular system or model of currency (e.g., monetary structure, denomination scheme, or valuation framework).
-
E.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
- F. None of above. chosen
Provenance (4 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49ff921288190a2e5edb201ba69ee |
completed | March 1, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69a49d18942c819083b3d1887e505900 |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49fcf0cb4819096edea4037ca2c03 |
completed | March 1, 2026, 8:21 p.m. |
Created at: March 1, 2026, 7:36 p.m.