Triple
T4831375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasserine |
E107952
|
entity |
| Predicate | hasHistoricalPeriodOfUnrest |
P42824
|
FINISHED |
| Object | January 2011 |
—
|
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: January 2011 | Statement: [Kasserine, hasHistoricalPeriodOfUnrest, January 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalPeriodOfUnrest Context triple: [Kasserine, hasHistoricalPeriodOfUnrest, January 2011]
-
A.
hasEthnicTensionHistory
Indicates that there has been a history of conflict, strain, or hostility between ethnic groups within the referenced context.
-
B.
hasMonthOfConflict
chosen
Indicates that a conflict is associated with, occurs in, or is characterized by a specific calendar month.
-
C.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
-
D.
hasCenterOfUprising
Indicates that a location serves as the main focal point or hub where an uprising or rebellion is centered or originates.
-
E.
religiousConflictPeriod
Indicates a period of time during which conflicts or hostilities occur that are primarily motivated or structured by religious differences or tensions.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.