Triple
T38401315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argonaut Mine disaster |
E900905
|
entity |
| Predicate | rescueAttemptFrom |
P122355
|
FINISHED |
| Object | Kennedy Mine |
—
|
NE NERFINISHED |
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: Kennedy Mine | Statement: [Argonaut Mine disaster, rescueAttemptFrom, Kennedy Mine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescueAttemptFrom Context triple: [Argonaut Mine disaster, rescueAttemptFrom, Kennedy Mine]
-
A.
attemptedRescueBy
chosen
Indicates an action where one entity made an effort to save or free another entity from danger, harm, or a problematic situation.
-
B.
rescueAttemptNumber
Indicates the ordinal count of distinct attempts made to carry out a rescue in a given rescue situation or operation.
-
C.
escapeAttempt
Indicates an action where an entity tries to get away from confinement, control, or a restricting situation.
-
D.
rescueFrom
Indicates that one entity saves or frees another entity from danger, harm, or an adverse situation.
-
E.
attemptedFrom
Indicates that an action or operation was initiated or tried starting from a particular source entity or location.
- 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_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.