Triple
T21599756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marias Massacre |
E533003
|
entity |
| Predicate | killedGroup |
P144126
|
FINISHED |
| Object | women |
—
|
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: women | Statement: [Marias Massacre, killedGroup, women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killedGroup Context triple: [Marias Massacre, killedGroup, women]
-
A.
killedBy
Indicates that one entity caused the death of another entity.
-
B.
killedAlongWith
Indicates that one entity was killed at the same time and in the same event or circumstance as another entity.
-
C.
killedDuring
Indicates that one entity caused the death of another entity in the course of, or as part of, a specified event or time period.
-
D.
killedBecauseOf
Indicates that one entity killed another specifically due to a particular reason, motive, or triggering factor associated with that other entity or a related circumstance.
-
E.
attemptedToKill
Indicates that one entity took deliberate action with the intention of causing the death of another entity, regardless of whether the death actually occurred.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefae4746c819090afe1d93fe9f175 |
completed | April 27, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63384a8fc819084c596bb53a3a1db |
completed | April 20, 2026, 2:09 p.m. |
Created at: April 16, 2026, 6:32 p.m.