Triple
T6895743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mapai-led coalition governments |
E159166
|
entity |
| Predicate | formedAlliancesWith |
P58850
|
FINISHED |
| Object | religious parties |
—
|
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: religious parties | Statement: [Mapai-led coalition governments, formedAlliancesWith, religious parties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedAlliancesWith Context triple: [Mapai-led coalition governments, formedAlliancesWith, religious parties]
-
A.
soughtAllianceWith
Indicates that one entity actively attempted to form an alliance or cooperative partnership with another entity.
-
B.
formedCoalitionWith
chosen
Indicates that two or more parties have joined together in a formal alliance or partnership to pursue shared goals or interests.
-
C.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
D.
reasonForAlliance
Indicates that one entity’s motivation, cause, or justification for forming an alliance is based on another specified factor or entity.
-
E.
laterAlliesWith
Indicates that two entities become allies at a later time, after not being allied initially.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d95ae3f88190b7f5d440f90ae9f9 |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.