Triple
T12423790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bende |
E296845
|
entity |
| Predicate | hasLocalLanguageGroup |
P3349
|
FINISHED |
| Object | Igbo language cluster |
—
|
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: Igbo language cluster | Statement: [Bende, hasLocalLanguageGroup, Igbo language cluster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalLanguageGroup Context triple: [Bende, hasLocalLanguageGroup, Igbo language cluster]
-
A.
hasLanguageGroup
chosen
Indicates that an entity belongs to, is associated with, or is categorized under a particular language group.
-
B.
hasSubLanguage
Indicates that one language is a subset, variant, or specialized form of another language.
-
C.
usesLocalLanguageVariant
Indicates that an entity employs a region-specific or localized form of a language rather than a standard or global variant.
-
D.
hasLocaleName
Indicates that an entity has a specific name or label used in a particular language or regional locale.
-
E.
hasLanguageCodeScope
Indicates that a language code is valid or applicable only within a specified scope, context, or domain.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e1888b48190bd750f839a26e99e |
completed | April 10, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69d94d354b488190adc83fb4f2770dd5 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.