Triple

T28754162
Position Surface form Disambiguated ID Type / Status
Subject Mario Sepúlveda E731619 entity
Predicate rescueEvent P91510 FINISHED
Object 2010 rescue of the 33 miners in Chile 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: 2010 rescue of the 33 miners in Chile | Statement: [Mario Sepúlveda, rescueEvent, 2010 rescue of the 33 miners in Chile]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rescueEvent
Context triple: [Mario Sepúlveda, rescueEvent, 2010 rescue of the 33 miners in Chile]
  • A. rescueBroadcast
    Indicates that one entity transmits an urgent communication intended to request or coordinate a rescue for another entity in distress.
  • B. resolutionEvent
    Indicates an event or action through which a previously existing issue, conflict, or problem is brought to a conclusion or resolved.
  • C. allegedRescueEvent
    Indicates that an event is claimed or reported to be a rescue, but its occurrence or nature is not confirmed as factual.
  • D. rescueBy chosen
    Indicates that one entity is saved or freed from danger, harm, or a problematic situation by another entity.
  • E. emergencyEvent
    Indicates that an urgent, unexpected, and potentially harmful situation or incident has occurred requiring immediate attention or response.
  • 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_69f043ed68a881909e858a06bab7a247 completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69f65f7731e4819099d5bd3d915ee266 completed May 2, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69f65c2198208190a3954086c22cfcbf completed May 2, 2026, 8:18 p.m.
Created at: April 28, 2026, 6:09 a.m.