Triple

T38401299
Position Surface form Disambiguated ID Type / Status
Subject Argonaut Mine disaster E900905 entity
Predicate deadliestInCategory P30647 FINISHED
Object one of the deadliest hard-rock mining accidents in U.S. history 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: one of the deadliest hard-rock mining accidents in U.S. history | Statement: [Argonaut Mine disaster, deadliestInCategory, one of the deadliest hard-rock mining accidents in U.S. history]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: deadliestInCategory
Context triple: [Argonaut Mine disaster, deadliestInCategory, one of the deadliest hard-rock mining accidents in U.S. history]
  • A. deadliestIn chosen
    Indicates that something has the highest lethality or causes the most deaths within a specified context, group, or location.
  • B. deadliestFor
    Indicates that one entity causes the greatest number of deaths or is most lethal specifically with respect to another entity or group.
  • C. fatalitiesCategory
    Indicates the classification of deaths associated with an event, incident, or condition into a specific category or severity level.
  • D. deathToll
    Indicates the number of deaths resulting from a particular event, situation, or cause.
  • E. deathBy
    Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
  • 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_69f76e6071a081909eea7a670d21420c completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fcd1499e2c81909bafd84dc4810f45 completed May 7, 2026, 5:52 p.m.
PD Predicate disambiguation batch_69fcccf024ec819086383ffbb6cfc036 completed May 7, 2026, 5:33 p.m.
Created at: May 3, 2026, 4:31 p.m.