Triple
T18137550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Council Decision 2011/199/EU |
E434175
|
entity |
| Predicate | concernsCurrency |
P4256
|
FINISHED |
| Object | euro |
—
|
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: euro | Statement: [European Council Decision 2011/199/EU, concernsCurrency, euro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsCurrency Context triple: [European Council Decision 2011/199/EU, concernsCurrency, euro]
-
A.
currencyOversight
Indicates that an entity has authority or responsibility to supervise, regulate, or manage the use, issuance, or stability of a currency.
-
B.
issuesCurrency
Indicates that an entity has the authority to create and put a specific currency into official circulation.
-
C.
involvesCurrency
chosen
Indicates that the relationship or action includes or pertains to the use, exchange, or specification of a particular currency.
-
D.
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).
-
E.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de089f1881908dff9835be5129a1 |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.