Triple
T15651569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Igboid |
E376323
|
entity |
| Predicate | hasDialectsWithinMajorLanguage |
P4251
|
FINISHED |
| Object | Central Igbo dialects |
—
|
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: Central Igbo dialects | Statement: [Igboid, hasDialectsWithinMajorLanguage, Central Igbo dialects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDialectsWithinMajorLanguage Context triple: [Igboid, hasDialectsWithinMajorLanguage, Central Igbo dialects]
-
A.
hasNumberOfDialects
Indicates the relationship between a language (or linguistic entity) and the count of distinct dialects it possesses.
-
B.
hasMajorDialectGroup
Indicates that an entity (typically a language) is associated with a primary or major dialect group to which it belongs.
-
C.
hasDialectsIn
Indicates that a language or linguistic variety possesses distinct dialects that are used or found within a specified region or context.
-
D.
hasDialects
chosen
Indicates that an entity (typically a language) possesses one or more distinct dialectal varieties.
-
E.
consideredDialectOf
Indicates that one language variety is regarded as a dialect of another language or linguistic 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eeed2d48190a7a8a618d90012d0 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.