Triple
T1996890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East African shilling |
E43378
|
entity |
| Predicate | iso4217Code |
P32242
|
FINISHED |
| Object | not yet assigned |
—
|
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: not yet assigned | Statement: [East African shilling, iso4217Code, not yet assigned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iso4217Code Context triple: [East African shilling, iso4217Code, not yet assigned]
-
A.
ISO4217Section
Indicates that something is associated with, defined in, or categorized under a specific section of the ISO 4217 currency standard.
-
B.
codeNumericISO4217
Indicates that an entity is associated with a specific ISO 4217 numeric currency code.
-
C.
ISO4217CurrencyCodeIssued
chosen
Indicates that a specific ISO 4217 currency code has been officially issued or assigned as a valid currency identifier.
-
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.
ISO4217CurrencyManaged
Indicates that an entity is responsible for administering, regulating, or overseeing a specific ISO 4217 currency.
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb91055d88190a980e7b42e5895d4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb79c97d48190b3147430ed39faa9 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.