Triple
T35054460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nieuwkerken-Waas |
E1011421
|
entity |
| Predicate | hasLocalCurrencyCode |
P189
|
FINISHED |
| Object | EUR |
—
|
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: EUR | Statement: [Nieuwkerken-Waas, hasLocalCurrencyCode, EUR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalCurrencyCode Context triple: [Nieuwkerken-Waas, hasLocalCurrencyCode, EUR]
-
A.
localCurrency
Indicates that a particular currency is officially used or recognized as the standard medium of exchange within a specific locality, region, or country.
-
B.
currencyNameLocal
Indicates the name of a currency as expressed in the local or native language of the region where it is used.
-
C.
hasISO4217Status
Indicates the classification or status of a currency according to the ISO 4217 standard.
-
D.
hasISOCode
chosen
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
-
E.
hasDominantCurrency
Indicates that one currency is the primary or controlling medium of exchange or valuation within a given context, such as a market, region, or financial system.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: May 3, 2026, 4:01 p.m.