Triple
T33777968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tugen people |
E865571
|
entity |
| Predicate | partOfEthnicCluster |
P90751
|
FINISHED |
| Object | Kalenjin people |
—
|
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: Kalenjin people | Statement: [Tugen people, partOfEthnicCluster, Kalenjin people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfEthnicCluster Context triple: [Tugen people, partOfEthnicCluster, Kalenjin people]
-
A.
ethnolinguisticCluster
chosen
Indicates a relationship where entities are grouped together based on shared ethnic and linguistic characteristics, treating them as part of the same ethnolinguistic cluster.
-
B.
containedEthnicGroup
Indicates that one entity (typically a larger group, region, or population) includes or encompasses a particular ethnic group within it.
-
C.
mayBelongToEthnicGroup
Indicates that an entity is possibly, but not certainly, a member of a specified ethnic group.
-
D.
nearEthnicGroup
Indicates that one entity is located geographically close to an ethnic group.
-
E.
commonInEthnicGroup
Indicates that something (such as a trait, condition, or characteristic) occurs with notable frequency within a specified ethnic group.
- 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_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: May 1, 2026, 1:45 a.m.