Triple
T2728333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zionist organizations |
E60248
|
entity |
| Predicate | aimTo |
P860
|
FINISHED |
| Object | strengthen ties between Jews and Israel |
—
|
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: strengthen ties between Jews and Israel | Statement: [Zionist organizations, aimTo, strengthen ties between Jews and Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimTo Context triple: [Zionist organizations, aimTo, strengthen ties between Jews and Israel]
-
A.
aimsToMeasure
Indicates that one entity is intended or designed to quantify, assess, or evaluate another entity or property.
-
B.
aimsToBalance
Indicates an intention or effort by one entity to bring multiple elements, forces, or conditions into a state of equilibrium.
-
C.
target
chosen
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
D.
aimOfAttacker
Indicates that a particular goal, target, or objective is what the attacker intends to achieve or affect.
-
E.
aimsToDevelop
Indicates an entity’s intention or effort to create, improve, or bring about another entity, outcome, or capability.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaeaee388190a21e7fa0b8f83546 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.