Triple
T34294537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lozi kingdom |
E879985
|
entity |
| Predicate | regainedControlFrom |
P23723
|
FINISHED |
| Object | Kololo 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: Kololo people | Statement: [Lozi kingdom, regainedControlFrom, Kololo people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regainedControlFrom Context triple: [Lozi kingdom, regainedControlFrom, Kololo people]
-
A.
transferredControlFrom
chosen
Indicates that authority or control over something has been moved or handed over from one entity to another.
-
B.
redefinedControlOver
Indicates that an entity has newly established or significantly altered authority, influence, or decision-making power over another entity or process.
-
C.
lostControlOfEvent
Indicates that an entity no longer has the ability to direct, manage, or influence the course or outcome of a particular event.
-
D.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
E.
regainedTitleFrom
Indicates that an entity has recovered a previously held title or position from another entity who had taken or held it in the interim.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.