Triple
T9193342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hissène Habré |
E220641
|
entity |
| Predicate | endOfRuleCause |
P54944
|
FINISHED |
| Object | military rebellion |
—
|
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: military rebellion | Statement: [Hissène Habré, endOfRuleCause, military rebellion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfRuleCause Context triple: [Hissène Habré, endOfRuleCause, military rebellion]
-
A.
endRule
Indicates that a previously active rule, regulation, or governing condition is terminated or ceases to apply.
-
B.
reasonForEndOfRule
chosen
Indicates the cause, circumstance, or event that led to the termination or conclusion of a particular rule or period of rule.
-
C.
endOfRuleContext
Indicates that a particular parsing or evaluation rule has reached its terminating boundary within the current context.
-
D.
typicalEndRule
Indicates the rule or condition that normally determines how or when a process, event, or relationship comes to an end.
-
E.
endRuleRegion
Indicates the point at which a previously defined rule’s applicable region or scope terminates.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd5c1fa9c8190bc5cc6dce8778694 |
completed | April 1, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.