Triple
T15037565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAD |
E378515
|
entity |
| Predicate | hasCurrencyCodeLength |
P116492
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [CAD, hasCurrencyCodeLength, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrencyCodeLength Context triple: [CAD, hasCurrencyCodeLength, 3]
-
A.
ISO 4217 code
Indicates the standardized three-letter currency code assigned to a monetary unit according to the ISO 4217 international standard.
-
B.
isUniqueWithinISO4217
Indicates that a currency-related value is unique and not duplicated within the set of ISO 4217 currency codes.
-
C.
currencyCodeDenoted
Indicates that a specific currency code is used to denote or represent a particular currency.
-
D.
hasISO4217Status
Indicates the classification or status of a currency according to the ISO 4217 standard.
-
E.
hasISOCode
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
- F. None of above. chosen
Provenance (4 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82cf3848190b0b2b6c9e65bc70b |
completed | April 15, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:59 a.m.