Triple
T21635980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malagasy franc |
E533958
|
entity |
| Predicate | wasDecimalized |
P7632
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Malagasy franc, wasDecimalized, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasDecimalized Context triple: [Malagasy franc, wasDecimalized, true]
-
A.
decimalisationDate
Indicates the date on which a system, currency, or measurement was converted to a decimal-based format.
-
B.
decimalized
chosen
Indicates that something has been converted into or expressed in decimal form, typically changing from another numeral or measurement system to a base-10 representation.
-
C.
redenominationDate
Indicates the date on which a currency or financial instrument undergoes a formal change in its nominal value or unit (redenomination).
-
D.
wasDevaluedIn
Indicates that the value or worth of an entity was reduced during a specified event, time period, or context.
-
E.
decimalizationRelatedTo
Indicates a relationship where one entity is connected to the process, consequences, or context of converting a system (typically currency or measurement) to a decimal-based format.
- 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef538ddb088190a3cba6fdc84c0ae8 |
completed | April 27, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.