Triple
T36342884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravensdale mine explosion of 1915 |
E894976
|
entity |
| Predicate | victimsOccupation |
P1786
|
FINISHED |
| Object | coal 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: coal miners | Statement: [Ravensdale mine explosion of 1915, victimsOccupation, coal miners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimsOccupation Context triple: [Ravensdale mine explosion of 1915, victimsOccupation, coal miners]
-
A.
victimOccupation
chosen
Indicates the profession or job role held by the person who is the victim in an event or incident.
-
B.
victimsOfCrime
Indicates that the subject has suffered harm or loss as a result of a criminal act committed by the object.
-
C.
victimGroup
Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
-
D.
hasPerpetratorOccupation
Indicates that the occupation or job role of the perpetrator involved in an act or incident is being specified.
-
E.
sufferedOccupationBy
Indicates that an entity experienced harm, hardship, or adverse conditions as a result of being occupied or controlled by another entity.
- 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.