Triple
T11113195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barak Government |
E262811
|
entity |
| Predicate | majorSecurityEvent |
P50697
|
FINISHED |
| Object | outbreak of the Second Intifada |
—
|
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: outbreak of the Second Intifada | Statement: [Barak Government, majorSecurityEvent, outbreak of the Second Intifada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorSecurityEvent Context triple: [Barak Government, majorSecurityEvent, outbreak of the Second Intifada]
-
A.
majorSecurityIssue
Indicates that the subject faces or causes a significant security vulnerability or threat.
-
B.
majorFlashpointIn
chosen
Indicates that an event, issue, or conflict serves as a primary source of tension or confrontation within a specified larger context or setting.
-
C.
notableProtectiveIncident
Indicates that a significant event occurred in which one entity protected or defended another in a notable or remarkable way.
-
D.
attackOccurred
Indicates that an act of aggression or violence was carried out by one party against another.
-
E.
significantEventType
Indicates the specific category or kind of major or noteworthy event associated with an entity or situation.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79aa523588190a25d241ccc6a9679 |
completed | April 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.