Triple
T26168262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UM |
E654319
|
entity |
| Predicate | hasAlpha3CodeRelated |
P43262
|
FINISHED |
| Object | UMI |
—
|
NE NERFINISHED |
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: UMI | Statement: [UM, hasAlpha3CodeRelated, UMI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlpha3CodeRelated Context triple: [UM, hasAlpha3CodeRelated, UMI]
-
A.
hasISO3166Alpha3Code
chosen
Indicates that an entity is associated with a specific three-letter country code defined by the ISO 3166-1 alpha-3 standard.
-
B.
linkedToISO3166-2CodesOf
Indicates a relationship where an entity is associated with, or mapped to, specific ISO 3166-2 subdivision codes that represent its corresponding administrative regions.
-
C.
hasISO4217ThreeLetterCode
Indicates that an entity is associated with a specific three-letter currency code defined by the ISO 4217 standard.
-
D.
sharesISO3166CodeWith
Indicates that two entities are associated with and use the same ISO 3166 country code.
-
E.
ISO3166Relation
Indicates a relationship that associates an entity with its corresponding ISO 3166 country or region code as defined by the international standard.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 26, 2026, 8:33 p.m.