Triple
T35858613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish community of Hebron |
E1036577
|
entity |
| Predicate | wasMassacredIn |
P154689
|
FINISHED |
| Object | 1929 Hebron massacre |
—
|
NE NERFINISHED |
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: 1929 Hebron massacre | Statement: [Jewish community of Hebron, wasMassacredIn, 1929 Hebron massacre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMassacredIn Context triple: [Jewish community of Hebron, wasMassacredIn, 1929 Hebron massacre]
-
A.
massacreOccurredIn
Indicates that a massacre took place within the specified location or area.
-
B.
massacreOccurred
Indicates that a large-scale, deliberate killing of multiple individuals took place in a specific event or context.
-
C.
massacreAlsoKnownAs
Indicates that a particular massacre is known or referred to by an alternative name or names.
-
D.
massacreDepictedIn
Indicates that a particular massacre is represented, shown, or portrayed within a specific work, such as a text, image, or audiovisual medium.
-
E.
massacreVictimsIncluded
chosen
Indicates that the set of victims in a massacre included the specified entities or group.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.