Triple
T31697134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kfar Etzion massacre |
E808946
|
entity |
| Predicate | combatantTargeted |
P174962
|
FINISHED |
| Object | Haganah members |
—
|
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: Haganah members | Statement: [Kfar Etzion massacre, combatantTargeted, Haganah members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantTargeted Context triple: [Kfar Etzion massacre, combatantTargeted, Haganah members]
-
A.
battleTarget
Indicates that one entity is the chosen opponent or objective that another entity is engaging or intends to engage in battle.
-
B.
coordinatedAttacksAlsoTargeted
Indicates that in a set of coordinated attacks, the same target was also attacked as part of those coordinated actions.
-
C.
civilianTarget
Indicates that the action or operation is directed at, affects, or designates civilians or civilian objects as the target.
-
D.
enemyTechnologyTargeted
Indicates that a technology belonging to an enemy is being specifically selected or targeted for attack, disruption, or counteraction.
-
E.
targetedForce
Indicates a deliberate application of force directed at a specific target or entity.
- F. None of above. chosen
Provenance (4 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: April 30, 2026, 11:10 p.m.