Triple

T846495
Position Surface form Disambiguated ID Type / Status
Subject Air Force Reserve E18286 entity
Predicate primaryEmployer P7 FINISHED
Object civilian sector 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: civilian sector | Statement: [Air Force Reserve, primaryEmployer, civilian sector]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryEmployer
Context triple: [Air Force Reserve, primaryEmployer, civilian sector]
  • A. formerEmployer
    Indicates that one entity previously employed the other but no longer does so.
  • B. employer chosen
    Indicates a relationship where one entity hires, pays, and oversees the work of another entity.
  • C. employerType
    Indicates the classification or category of an employer in relation to the entity (e.g., public, private, nonprofit, self-employed).
  • D. residentCompany
    Indicates that a company is based in, operates from, or has its primary residence in a particular location or jurisdiction.
  • E. employmentType
    Indicates the specific kind or category of employment relationship that exists between an individual and an employer (e.g., full-time, part-time, contract).
  • 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_69a4938b04208190b82e1df6b572c548 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac0ba6b4819089c15ed7e1765502 completed March 1, 2026, 9:13 p.m.
PD Predicate disambiguation batch_69a4aa7f396c8190aa8b8dfbe0b4f732 completed March 1, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:38 p.m.