Triple
T6040848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hutu |
E134538
|
entity |
| Predicate | preColonialSystem |
P15768
|
FINISHED |
| Object | part of Rwandan monarchy |
—
|
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: part of Rwandan monarchy | Statement: [Hutu, preColonialSystem, part of Rwandan monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preColonialSystem Context triple: [Hutu, preColonialSystem, part of Rwandan monarchy]
-
A.
precolonialPolity
Indicates that an entity functioned as a political or governing unit during the period before colonial rule was established in its region.
-
B.
preColonialUse
Indicates that something was used or occupied in a particular way during the period before colonial rule or colonization.
-
C.
preColonialStatus
chosen
Indicates the condition, role, or social-political standing an entity held prior to the onset of colonial rule.
-
D.
colonialLegacy
Indicates the enduring influence or consequences of a past colonial relationship that continue to shape interactions or conditions between entities.
-
E.
formerColonialEntity
Indicates that one entity was previously a colony or colonial possession of another entity.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056cf82d481909d5161fe3643e7ed |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049eb52a08190ac10fd703735f5aa |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.