Triple
T35367725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kololo people |
E1021680
|
entity |
| Predicate | timeOfPoliticalDominance |
P5898
|
FINISHED |
| Object | mid-19th century |
—
|
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: mid-19th century | Statement: [Kololo people, timeOfPoliticalDominance, mid-19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfPoliticalDominance Context triple: [Kololo people, timeOfPoliticalDominance, mid-19th century]
-
A.
timePeriodOfDominance
chosen
Indicates the span of time during which an entity held dominance, control, or prevailing influence over another entity or context.
-
B.
periodOfRule
Indicates the span of time during which an entity exercised authority, control, or governance over something.
-
C.
reignOrLeadershipPeriod
Indicates the time span during which an entity holds ruling authority or leadership over a group, organization, or territory.
-
D.
dynastyRuled
Indicates that a particular dynasty held ruling authority or governance over a specified region, state, or people during a certain period.
-
E.
historicalPower
Indicates that one entity held significant influence, control, or authority over another during a past 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: May 3, 2026, 4:03 p.m.