Triple
T33342151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bantu Zone B |
E853698
|
entity |
| Predicate | hasLanguageCluster |
P152634
|
FINISHED |
| Object | Kongo languages |
—
|
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: Kongo languages | Statement: [Bantu Zone B, hasLanguageCluster, Kongo languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageCluster Context triple: [Bantu Zone B, hasLanguageCluster, Kongo languages]
-
A.
includesLanguageCluster
chosen
Indicates that one entity contains or encompasses a specific group or cluster of related languages as part of its composition or scope.
-
B.
hasLanguageGroup
Indicates that an entity belongs to, is associated with, or is categorized under a particular language group.
-
C.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
-
D.
hasLanguageIsolate
Indicates that an entity’s language is not demonstrably related to any other known language family, standing as a unique linguistic isolate.
-
E.
hasLanguages
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:34 a.m.