Triple

T38226510
Position Surface form Disambiguated ID Type / Status
Subject Navy warrant officers E1012159 entity
Predicate typicalSourceOfRecruitment P4145 FINISHED
Object senior enlisted personnel 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: senior enlisted personnel | Statement: [Navy warrant officers, typicalSourceOfRecruitment, senior enlisted personnel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalSourceOfRecruitment
Context triple: [Navy warrant officers, typicalSourceOfRecruitment, senior enlisted personnel]
  • A. recruitmentFrom chosen
    Indicates that one entity recruits or sources members, employees, or participants from another entity.
  • B. recruitmentMethods
    Indicates the ways or strategies used to attract, source, and enlist individuals for a role, program, or organization.
  • C. canBeRecruitedFrom
    Indicates that one entity is eligible to be recruited, obtained, or enlisted starting from or via another specified entity or source.
  • D. recruitmentBase
    Indicates the foundational source, location, or context from which recruitment efforts or recruited entities originate.
  • E. recruit
    Indicates bringing a person or group into an organization, cause, or activity, typically to join or participate.
  • 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_69f76dd25e0c81909f2abd0803e5e3ee completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a037c903be48190a2fafa53d7d50d42 completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a1c850c819088795a7ae59bdeb8 completed May 12, 2026, 7:06 p.m.
Created at: May 3, 2026, 4:30 p.m.