Triple

T36636770
Position Surface form Disambiguated ID Type / Status
Subject William H. Pitsenbarger E904483 entity
Predicate militaryOccupationSpecialty P9463 FINISHED
Object pararescue (PJ) 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: pararescue (PJ) | Statement: [William H. Pitsenbarger, militaryOccupationSpecialty, pararescue (PJ)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: militaryOccupationSpecialty
Context triple: [William H. Pitsenbarger, militaryOccupationSpecialty, pararescue (PJ)]
  • A. hasMilitarySpeciality
    Indicates that an entity possesses a specific military role, skill set, or area of professional expertise within the armed forces.
  • B. militaryRole chosen
    Indicates the specific function, position, or duty an entity holds within a military organization or context.
  • C. hasMilitaryDesignation
    Indicates that an entity is assigned a specific military-related code, title, or classification.
  • D. isMilitaryOffice
    Indicates that an entity holds or is designated as a military office or official position within an armed forces structure.
  • E. isMilitaryOrderGrade
    Indicates that one entity is classified as a specific grade or level within a military order or honor system in relation to another entity.
  • 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_69f76e6c63e48190b1d0c3a79a6c7406 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fd231cab588190ad0953dc8f4af8f2 completed May 7, 2026, 11:41 p.m.
PD Predicate disambiguation batch_69fd1aa3f1c481909fe6e9cab1383551 completed May 7, 2026, 11:05 p.m.
Created at: May 3, 2026, 4:11 p.m.