Triple
T21635979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malagasy franc |
E533958
|
entity |
| Predicate | hasFormerISO4217Code |
P15239
|
FINISHED |
| Object | MGF |
—
|
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: MGF | Statement: [Malagasy franc, hasFormerISO4217Code, MGF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerISO4217Code Context triple: [Malagasy franc, hasFormerISO4217Code, MGF]
-
A.
formerISO4217Code
chosen
Indicates that an entity was previously assigned a particular ISO 4217 currency code that is no longer in current use for it.
-
B.
hasISO4217Status
Indicates the classification or status of a currency according to the ISO 4217 standard.
-
C.
ISO 4217 code
Indicates the standardized three-letter currency code assigned to a monetary unit according to the ISO 4217 international standard.
-
D.
ISO4217CurrencyCodeIssued
Indicates that a specific ISO 4217 currency code has been officially issued or assigned as a valid currency identifier.
-
E.
successorISO4217Code
Indicates that one currency’s ISO 4217 code has been officially replaced by another currency’s ISO 4217 code as its successor.
- 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.