Triple
T2163744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COP |
E46859
|
entity |
| Predicate | introducedAsISOCodeIn |
P36095
|
FINISHED |
| Object | ISO 4217 first edition |
—
|
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: ISO 4217 first edition | Statement: [COP, introducedAsISOCodeIn, ISO 4217 first edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsISOCodeIn Context triple: [COP, introducedAsISOCodeIn, ISO 4217 first edition]
-
A.
hasISOCode
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
-
B.
previousISOCode
Indicates that an entity was formerly identified by a different ISO code before its current one.
-
C.
currentISOCodeEffectiveFrom
Indicates the date and time from which the current ISO code for an entity becomes valid or officially in effect.
-
D.
formerISO4217Code
Indicates that an entity was previously assigned a particular ISO 4217 currency code that is no longer in current use for it.
-
E.
sharesISO3166CodeWith
Indicates that two entities are associated with and use the same ISO 3166 country code.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe8d105c819098371c35c88873dc |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe1ecb7081909c2c66da08a48ab7 |
completed | March 7, 2026, 5:56 a.m. |
Created at: March 4, 2026, 7:45 p.m.