Triple
T33778024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lembus |
E865572
|
entity |
| Predicate | belongsToDialectCluster |
P197362
|
FINISHED |
| Object | Kalenjin dialect 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: Kalenjin dialect cluster | Statement: [Lembus, belongsToDialectCluster, Kalenjin dialect cluster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToDialectCluster Context triple: [Lembus, belongsToDialectCluster, Kalenjin dialect cluster]
-
A.
isPartOfDialectCluster
chosen
Indicates that one dialect belongs to, or is included within, a larger group of closely related dialects.
-
B.
hasDialectCluster
Indicates that one language or linguistic variety is associated with a particular group or cluster of related dialects.
-
C.
associatedWithDialectGroup
Indicates that one entity is connected or related to a particular dialect group, typically through usage, origin, or classification.
-
D.
isDialectalBaseOf
Indicates that one language variety serves as the primary dialectal source or foundation from which another dialect develops or is derived.
-
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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: May 1, 2026, 1:45 a.m.