Triple

T4346953
Position Surface form Disambiguated ID Type / Status
Subject First Lieutenant E97927 entity
Predicate payGradeInUSArmy P7397 FINISHED
Object O-2 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: O-2 | Statement: [First Lieutenant, payGradeInUSArmy, O-2]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: payGradeInUSArmy
Context triple: [First Lieutenant, payGradeInUSArmy, O-2]
  • A. payGrade chosen
    Indicates the level or category of compensation assigned to an entity, typically reflecting its rank, role, or seniority in a pay structure.
  • B. militaryRank
    Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
  • C. payGradeComparison
    Indicates that the relative pay grade or salary level between two entities is being compared (e.g., one is higher, lower, or equal to the other).
  • D. isMilitaryRank
    Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
  • E. militaryRankProgression
    Indicates the sequence or advancement of an individual’s positions within a structured military rank hierarchy.
  • 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_69b34548402c819085ab68b27c235a87 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3518d6728819084a2f40ae0bd3ac8 completed March 12, 2026, 11:51 p.m.
PD Predicate disambiguation batch_69b34f4fe1c481908d6d66e15697c04b completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:15 p.m.