Triple
T901280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsmill massacre |
E19450
|
entity |
| Predicate | victimCountProtestant |
P1785
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Kingsmill massacre, victimCountProtestant, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimCountProtestant Context triple: [Kingsmill massacre, victimCountProtestant, 10]
-
A.
notableVictim
Indicates that the subject is a person or entity who is notably recognized as a victim of the object (such as an event, crime, or harmful action).
-
B.
notableVictims
Indicates that the object is a person or group who is especially well-known or significant as a victim of the subject.
-
C.
statusInMainlineProtestantism
Indicates the recognized standing, role, or level of acceptance an entity has within mainline Protestant Christian traditions.
-
D.
deathToll
chosen
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
E.
persecutedDuring
Indicates that one entity systematically harassed, oppressed, or victimized another entity during a specified time period or event.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad4412408190a6bf8fc7484a5781 |
completed | March 1, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69a4aa979d408190b17ccfde132ea628 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.