Triple
T28970579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorado Coalfield War |
E734258
|
entity |
| Predicate | notableFatalities |
P19083
|
FINISHED |
| Object | striking miners |
—
|
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: striking miners | Statement: [Colorado Coalfield War, notableFatalities, striking miners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFatalities Context triple: [Colorado Coalfield War, notableFatalities, striking miners]
-
A.
notableDeath
Indicates that an entity’s death is considered significant or noteworthy in some context.
-
B.
notableVictims
chosen
Indicates that the object is a person or group who is especially well-known or significant as a victim of the subject.
-
C.
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).
-
D.
notablePersonKilledThere
Indicates that a notable or famous person was killed at the referenced location.
-
E.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a01ca0db6f08190bed479584114e63d |
completed | May 11, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_6a01c96ff4a08190a4fbf0cebbda95b4 |
completed | May 11, 2026, 12:20 p.m. |
Created at: April 28, 2026, 9:05 a.m.