Triple
T32266773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zintani armed coalitions |
E824307
|
entity |
| Predicate | roleIn2011Uprising |
P88009
|
FINISHED |
| Object | major military role |
—
|
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: major military role | Statement: [Zintani armed coalitions, roleIn2011Uprising, major military role]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleIn2011Uprising Context triple: [Zintani armed coalitions, roleIn2011Uprising, major military role]
-
A.
hasCenterOfUprising
Indicates that a location serves as the main focal point or hub where an uprising or rebellion is centered or originates.
-
B.
typeOfUprisingLed
Indicates the specific kind or category of uprising that a leader was responsible for directing or organizing.
-
C.
resultOfUprising
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
D.
roleInRiseAgainst
Indicates that an entity held a specific role or position within the group or organization known as Rise Against.
-
E.
roleInRevolt
chosen
Indicates the specific function, position, or level of participation an entity had within a particular revolt or uprising.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: May 1, 2026, 12:42 a.m.