Triple
T22717934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legrand |
E561782
|
entity |
| Predicate | usesReportingCurrency |
P188
|
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: [Legrand, usesReportingCurrency, euro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesReportingCurrency Context triple: [Legrand, usesReportingCurrency, euro]
-
A.
usesCurrency
chosen
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
B.
usesCurrencyInitially
Indicates that an entity originally adopts or operates with a particular currency at the start of a defined period or process.
-
C.
currencyUsedFor
Indicates that a particular currency is used as the medium of exchange or legal tender for a given entity, such as a country, region, or organization.
-
D.
usesSupplementaryCurrency
Indicates that an entity employs an additional, non-primary currency alongside its main currency for transactions or value exchange.
-
E.
inUniverseCurrencyUse
Indicates that a currency is used as legal tender or medium of exchange within a particular fictional or defined universe.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790ecbc48190926d16b20b674dbd |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:19 p.m.