Triple
T21599779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marias Massacre |
E533003
|
entity |
| Predicate | actualTarget |
P815
|
FINISHED |
| Object | Heavy Runner’s band |
—
|
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: Heavy Runner’s band | Statement: [Marias Massacre, actualTarget, Heavy Runner’s band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualTarget Context triple: [Marias Massacre, actualTarget, Heavy Runner’s band]
-
A.
acquisitionTarget
Indicates that one entity is the intended or actual company or asset being acquired by another in a merger or acquisition transaction.
-
B.
primaryTarget
chosen
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
C.
plannedTarget
Indicates that one entity has been designated or selected as the intended target or objective of another entity’s planned action or operation.
-
D.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
E.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
- 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_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. |
Created at: April 16, 2026, 6:32 p.m.