Triple
T34242472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Netanyahu Government |
E878502
|
entity |
| Predicate | coalitionCrisisCause |
P51764
|
FINISHED |
| Object | disputes over 2015 budget |
—
|
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: disputes over 2015 budget | Statement: [Third Netanyahu Government, coalitionCrisisCause, disputes over 2015 budget]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coalitionCrisisCause Context triple: [Third Netanyahu Government, coalitionCrisisCause, disputes over 2015 budget]
-
A.
causeOfPoliticalConflict
chosen
Indicates that one entity is the source or reason for a political conflict involving another entity.
-
B.
coalitionBase
Indicates that one entity serves as the foundational or primary support group upon which a broader coalition or alliance is built.
-
C.
coalitionType
Indicates the specific kind or category of coalition relationship that exists between the involved entities.
-
D.
coalitionPotential
Indicates the potential or likelihood that two or more entities can form a cooperative alliance or coalition.
-
E.
coalitionLevel
Indicates the degree or intensity of cooperative alignment or partnership between entities within a coalition.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.