Triple
T37436201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marakwet people |
E930275
|
entity |
| Predicate | traditionalConflictHistoryWith |
P37642
|
FINISHED |
| Object | Pokot 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: Pokot people | Statement: [Marakwet people, traditionalConflictHistoryWith, Pokot people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalConflictHistoryWith Context triple: [Marakwet people, traditionalConflictHistoryWith, Pokot people]
-
A.
conflictHistory
chosen
Indicates a history of conflict or antagonistic interactions that have occurred between the related entities.
-
B.
linkedToHistoricalConflict
Indicates that one entity has a documented association or connection with a past historical conflict involving another entity.
-
C.
hasHistoricalPeriodOfConflict
Indicates that there exists a specific historical period during which the related entities were engaged in conflict or hostilities.
-
D.
conflictEra
Indicates that two entities are associated with the same historical period or era of conflict.
-
E.
loreConflict
Indicates that there is an inconsistency, contradiction, or incompatibility between pieces of lore or canonical information.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
Created at: May 3, 2026, 4:17 p.m.