Triple
T12603306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alliance of Democratic Forces for the Liberation of Congo-Zaire |
E300911
|
entity |
| Predicate | seizedPowerOn |
P12797
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Alliance of Democratic Forces for the Liberation of Congo-Zaire, seizedPowerOn, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seizedPowerOn Context triple: [Alliance of Democratic Forces for the Liberation of Congo-Zaire, seizedPowerOn, 1997]
-
A.
seizedPowerBy
Indicates that one entity took control or authority from another, typically through force, coercion, or other non-consensual means.
-
B.
seizedPowerAfter
Indicates that one entity took control or authority from another entity following a specified event or point in time.
-
C.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
D.
inPowerSince
chosen
Indicates the point in time from which an entity has continuously held a position of authority or power.
-
E.
seizedCapital
Indicates that one entity forcibly took control of another entity’s capital city.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:10 p.m.