Triple
T14815617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embu people |
E348305
|
entity |
| Predicate | resistanceHistory |
P55657
|
FINISHED |
| Object | participation in Mau Mau uprising |
—
|
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: participation in Mau Mau uprising | Statement: [Embu people, resistanceHistory, participation in Mau Mau uprising]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resistanceHistory Context triple: [Embu people, resistanceHistory, participation in Mau Mau uprising]
-
A.
regionBefore1945
Indicates that one region existed or was defined in a particular way prior to the year 1945.
-
B.
resistedUntil
Indicates that an entity continued to oppose or withstand another entity or force up to a specific point in time or event.
-
C.
resistanceOrganization
Indicates an organization that actively opposes, resists, or fights against a dominant power, regime, or occupying force.
-
D.
resistedIn
chosen
Indicates that an entity actively opposed, withstood, or fought against something within a specific context, event, or location.
-
E.
historicallyOpposedBy
Indicates that one entity has been the target of opposition, resistance, or antagonism from another entity over a historical period.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe0e89c81908c0e1fe2bc3ebcfc |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:49 a.m.