Triple

T32185658
Position Surface form Disambiguated ID Type / Status
Subject Airman First Class (USSF enlisted rank) E822101 entity
Predicate isWarrantOfficerRank P109149 FINISHED
Object no 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: no | Statement: [Airman First Class (USSF enlisted rank), isWarrantOfficerRank, no]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isWarrantOfficerRank
Context triple: [Airman First Class (USSF enlisted rank), isWarrantOfficerRank, no]
  • A. warrantOfficer
    Indicates that one entity holds the military rank or position of warrant officer in relation to another entity (such as an organization, unit, or force).
  • B. hasWarrantOrNCOEquivalentRank chosen
    Indicates that one entity holds a warrant officer rank or an equivalent non-commissioned officer rank in relation to another entity.
  • C. isWartimeRank
    Indicates that a given military rank is designated for use specifically during periods of war or armed conflict, rather than in peacetime.
  • D. isMilitaryRank
    Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
  • E. isMilitaryOfficer
    Indicates that the subject holds an official position as an officer within a military organization.
  • 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_69f3490755288190aee11740a34862f9 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bab9100c8190ad1f86fece0fc505 completed May 3, 2026, 3:02 a.m.
PD Predicate disambiguation batch_69f6b3aa892481908d29283a074e6722 completed May 3, 2026, 2:32 a.m.
Created at: May 1, 2026, 12:35 a.m.