Triple
T3769456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Currency Unit |
E82760
|
entity |
| Predicate | conversionMethodToEuro |
P9578
|
FINISHED |
| Object | 1 ECU = 1 euro at transition |
—
|
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: 1 ECU = 1 euro at transition | Statement: [European Currency Unit, conversionMethodToEuro, 1 ECU = 1 euro at transition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionMethodToEuro Context triple: [European Currency Unit, conversionMethodToEuro, 1 ECU = 1 euro at transition]
-
A.
fixedConversionRateToEuro
chosen
Indicates that one currency has a fixed, predetermined exchange rate relative to the euro.
-
B.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
-
C.
exchangeRateToPapiermark
Indicates the conversion rate or value of one currency in terms of the Papiermark.
-
D.
currencyPractice
Indicates the customary or standard way a particular currency is used, represented, or managed in transactions or economic contexts.
-
E.
currencyForm
Indicates that one entity is a specific monetary form, denomination, or variant of the currency represented by the other entity.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc2f016c81909c2e3c85dbc3c259 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.