Triple
T7866992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyamwezi people |
E182640
|
entity |
| Predicate | MiramboRole |
P79446
|
FINISHED |
| Object | 19th-century Nyamwezi warlord |
—
|
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: 19th-century Nyamwezi warlord | Statement: [Nyamwezi people, MiramboRole, 19th-century Nyamwezi warlord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MiramboRole Context triple: [Nyamwezi people, MiramboRole, 19th-century Nyamwezi warlord]
-
A.
roleInBladeII
Indicates that an entity has a specific role or participation in the movie "Blade II."
-
B.
LakatoroRole
Indicates that an entity holds or is assigned a specific role or function within the context of Lakatoro.
-
C.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
D.
roleAtMidway
Indicates that an entity holds or held a specific role, position, or function at the midpoint or intermediate stage of a process, event, or time period.
-
E.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
- F. None of above. chosen
Provenance (4 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb38464274819080f182b53783fa84 |
completed | March 31, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:54 p.m.