Triple

T31744377
Position Surface form Disambiguated ID Type / Status
Subject V-bomber force E810228 entity
Predicate ValiantRetirementReason P16517 FINISHED
Object metal fatigue issues 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: metal fatigue issues | Statement: [V-bomber force, ValiantRetirementReason, metal fatigue issues]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ValiantRetirementReason
Context triple: [V-bomber force, ValiantRetirementReason, metal fatigue issues]
  • A. forcedToRetire chosen
    Indicates that an entity was compelled, rather than choosing voluntarily, to end their professional role or career.
  • B. retirementType
    Indicates the specific category or manner in which an entity retires or is retired (e.g., voluntary, mandatory, early).
  • C. retirementDate
    Indicates the date on which an entity stops its active role or service, typically marking the end of its professional or operational period.
  • D. retiredFrom
    Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
  • E. retiredTo
    Indicates that an entity has permanently left active service or work and taken up residence or status in a particular place or role as their retirement destination.
  • 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_69f348e233cc819083b6695f70cd75d8 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6afebd7ec8190ab696f363d84abf0 completed May 3, 2026, 2:16 a.m.
PD Predicate disambiguation batch_69f6aca3dedc81908b519d53d2909868 completed May 3, 2026, 2:02 a.m.
Created at: April 30, 2026, 11:26 p.m.