Triple
T17752237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTL |
E443139
|
entity |
| Predicate | successorCurrencyName |
P89148
|
FINISHED |
| Object | Euro |
—
|
NE NERFINISHED |
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: Euro | Statement: [LTL, successorCurrencyName, Euro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Euro Context triple: [LTL, successorCurrencyName, Euro]
-
A.
Euro
chosen
The Euro is the official common currency used by many countries in the European Union, facilitating trade and travel across much of Europe.
-
B.
Eurozone
The Eurozone is the group of European Union countries that have adopted the euro as their common official currency and share a unified monetary policy.
-
C.
EU
EU is the vehicle registration code for the German district of Euskirchen in the state of North Rhine-Westphalia.
-
D.
EURO
EURO is the commonly used abbreviation for the World Health Organization’s Regional Office for Europe, which oversees public health initiatives across the European region.
-
E.
EURO
EURO is the commonly used short name for the UEFA European Championship, the premier international football tournament for national teams in Europe.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841b3ccc8190b3241b3e0fa4b2e8 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 10:10 a.m.