Triple
T31697147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kfar Etzion massacre |
E808946
|
entity |
| Predicate | statusOfVictims |
P58515
|
FINISHED |
| Object | surrendered combatants |
—
|
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: surrendered combatants | Statement: [Kfar Etzion massacre, statusOfVictims, surrendered combatants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfVictims Context triple: [Kfar Etzion massacre, statusOfVictims, surrendered combatants]
-
A.
legalStatusOfVictims
Indicates the legal classification or condition of the victims in relation to the event or action described.
-
B.
hasVictims
Indicates that an entity has one or more individuals who have been harmed, injured, or adversely affected by it.
-
C.
mainVictims
Indicates that the related entities are the primary or principal targets harmed or affected by an action, event, or perpetrator.
-
D.
victimStatus
chosen
Indicates the condition or state of a person who has been harmed or wronged as a result of an event, action, or offense.
-
E.
numberOfSuspectedVictims
Indicates the count of individuals believed or alleged to be victims in a particular incident, case, or context.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: April 30, 2026, 11:10 p.m.