Triple
T2163851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COL$ |
E46862
|
entity |
| Predicate | representsISO4217Code |
P189
|
FINISHED |
| Object | COP |
—
|
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: COP | Statement: [COL$, representsISO4217Code, COP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsISO4217Code Context triple: [COL$, representsISO4217Code, COP]
-
A.
representsISOName
Indicates that one entity denotes or encodes the standardized ISO-compliant name of another entity.
-
B.
formerISO4217Code
Indicates that an entity was previously assigned a particular ISO 4217 currency code that is no longer in current use for it.
-
C.
codeNumericISO4217
Indicates that an entity is associated with a specific ISO 4217 numeric currency code.
-
D.
hasISOCode
chosen
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
-
E.
ISO4217CurrencyCodeIssued
Indicates that a specific ISO 4217 currency code has been officially issued or assigned as a valid currency identifier.
- 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_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. |
Created at: March 4, 2026, 7:45 p.m.