Triple

T27798920
Position Surface form Disambiguated ID Type / Status
Subject ApplicationMaster E702186 entity
Predicate failureHandledBy P163366 FINISHED
Object ResourceManager relaunching new attempt 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: ResourceManager relaunching new attempt | Statement: [ApplicationMaster, failureHandledBy, ResourceManager relaunching new attempt]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: failureHandledBy
Context triple: [ApplicationMaster, failureHandledBy, ResourceManager relaunching new attempt]
  • A. failureBehavior
    Indicates how a system, component, or process is expected to respond or act when a failure or error condition occurs.
  • B. failedOn
    Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
  • C. failureCrystallizedBy
    Indicates that a failure or breakdown is concretely manifested, solidified, or made clearly observable through a particular event, condition, or outcome.
  • D. failureCause
    Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
  • E. handledIn
    Indicates that an action, request, or process is managed, processed, or resolved within a particular context, location, system, or jurisdiction.
  • F. None of above. chosen

Provenance (4 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_69ef8408e0588190977cffa32dc33a29 completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69f6380d35bc81908444d5038af3ffcb completed May 2, 2026, 5:44 p.m.
PD Predicate disambiguation batch_69f6318ae6f08190b3f85f9201046a15 completed May 2, 2026, 5:16 p.m.
PDg Predicate description generation batch_69f6359d46b88190922dd7de508e3b0e completed May 2, 2026, 5:34 p.m.
Created at: April 27, 2026, 5:33 p.m.