Triple
T1263919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euro |
E12559
|
entity |
| Predicate | introducedAsBookCurrency |
P8013
|
FINISHED |
| Object | 1999-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: 1999-01-01 | Statement: [Euro, introducedAsBookCurrency, 1999-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsBookCurrency Context triple: [Euro, introducedAsBookCurrency, 1999-01-01]
-
A.
introducedAsModernCurrency
chosen
Indicates that an entity was established or adopted for use as a modern form of currency.
-
B.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
-
C.
currencyInitiative
Indicates an initiative, program, or action specifically related to the development, regulation, promotion, or reform of a currency or monetary system.
-
D.
currencyDepicted
Indicates that one entity visually represents or shows the image or symbol of a particular currency on it.
-
E.
previousCurrency
Indicates that one currency served as the predecessor or was replaced by another currency in a monetary system or sequence.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc8d6908190a5b2cf1051cc6d5e |
completed | March 1, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69a4bb7058e88190825b0cba5ee60b51 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:50 p.m.