Triple
T12387841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ihitte/Uboma |
E295913
|
entity |
| Predicate | hasISOCodeLevel |
P104687
|
FINISHED |
| Object | NG-IM |
—
|
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: NG-IM | Statement: [Ihitte/Uboma, hasISOCodeLevel, NG-IM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISOCodeLevel Context triple: [Ihitte/Uboma, hasISOCodeLevel, NG-IM]
-
A.
hasISOCode
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
-
B.
hasISOCodeType
Indicates that an entity is associated with a specific type or category of ISO code (e.g., country code, currency code, language code).
-
C.
isLegalISOCode
Indicates that a given code conforms to the ISO standard format and is officially recognized as a valid ISO code.
-
D.
hasISO639_5Code
Indicates that a language or language group is associated with a specific ISO 639-5 code that identifies it within the ISO 639-5 language classification standard.
-
E.
isCurrentISOCode
Indicates that an entity’s code is the officially recognized, up-to-date ISO standard code for that entity.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fcf6aa8819080c9a2407a72db2e |
completed | April 10, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93fa244148190a960be3ff6f1cf45 |
completed | April 10, 2026, 6:21 p.m. |
Created at: April 8, 2026, 9:54 p.m.