Triple
T357032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malaysian ringgit |
E7566
|
entity |
| Predicate | decimalization |
P7632
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Malaysian ringgit, decimalization, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decimalization Context triple: [Malaysian ringgit, decimalization, yes]
-
A.
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.
-
B.
denomination
Indicates the specific religious or organizational branch, sect, or subgroup with which an entity is affiliated.
-
C.
decimalisationDate
Indicates the date on which a system, currency, or measurement was converted to a decimal-based format.
-
D.
denominationSystem
Indicates a relationship where one entity defines, uses, or belongs to a particular system of denominations (such as units, values, or classifications) established by another entity.
-
E.
centralToDenomination
Indicates that something is a core or defining element within a particular religious denomination.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebaf0c9881909313f98818e7fa58 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e959ce948190a201c017eecb7c95 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.