Triple
T901264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsmill massacre |
E19450
|
entity |
| Predicate | perpetratorDisguise |
P5541
|
FINISHED |
| Object | British Army uniforms |
—
|
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: British Army uniforms | Statement: [Kingsmill massacre, perpetratorDisguise, British Army uniforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perpetratorDisguise Context triple: [Kingsmill massacre, perpetratorDisguise, British Army uniforms]
-
A.
perpetratedBy
Indicates that an action, event, or wrongdoing was carried out or caused by a particular agent or entity.
-
B.
methodOfDisappearance
Indicates the specific way or process by which an entity ceases to be present, visible, or existent.
-
C.
defacedWith
Indicates that one entity has been damaged, marred, or vandalized using another entity as the means or material of defacement.
-
D.
costumeType
chosen
Indicates the specific kind or category of costume associated with an entity.
-
E.
protagonistAlterEgoOf
Indicates that one entity is the alternate identity or secret persona of the main character (protagonist) in a narrative.
- 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.