Triple
T2131163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RM |
E46541
|
entity |
| Predicate | currencyCodeType |
P15021
|
FINISHED |
| Object | historical |
—
|
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: historical | Statement: [RM, currencyCodeType, historical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyCodeType Context triple: [RM, currencyCodeType, historical]
-
A.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
B.
codeNumericISO4217
Indicates that an entity is associated with a specific ISO 4217 numeric currency code.
-
C.
currencyCodeStatus
chosen
Indicates the current validity or operational state of a specified currency code within a given system or context.
-
D.
currencyNumber
Indicates the numerical value or denomination associated with a specific currency.
-
E.
currencyModel
Indicates that something uses, is based on, or conforms to a particular system or model of currency (e.g., monetary structure, denomination scheme, or valuation framework).
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb79f21881909ad8d1a09c1f29fd |
completed | March 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_69abb7bf56e481909b0f497d238451cc |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.