Triple
T32779792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubossary |
E838320
|
entity |
| Predicate | usesCurrencyDeJure |
P188
|
FINISHED |
| Object | Moldovan leu |
—
|
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: Moldovan leu | Statement: [Dubossary, usesCurrencyDeJure, Moldovan leu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCurrencyDeJure Context triple: [Dubossary, usesCurrencyDeJure, Moldovan leu]
-
A.
usesCurrency
chosen
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
B.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
C.
currencyOnboard
Indicates that a particular currency has been enabled, registered, or made available for use within a given system or context.
-
D.
usesCurrentCurrenciesOf
Indicates that one entity adopts and operates with the same official currencies that are currently in use in another entity.
-
E.
usesCurrencyInitially
Indicates that an entity originally adopts or operates with a particular currency at the start of a defined period or process.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 1, 2026, 1:14 a.m.