Triple

T6627238
Position Surface form Disambiguated ID Type / Status
Subject Hero of Bennington E149833 entity
Predicate hasMilitaryRankOfDesignee P342 FINISHED
Object brigadier general 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: brigadier general | Statement: [Hero of Bennington, hasMilitaryRankOfDesignee, brigadier general]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMilitaryRankOfDesignee
Context triple: [Hero of Bennington, hasMilitaryRankOfDesignee, brigadier general]
  • A. isMilitaryRank
    Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
  • B. hasMilitaryDesignation
    Indicates that an entity is assigned a specific military-related code, title, or classification.
  • C. militaryRankEligibility
    Indicates that one entity is qualified or permitted to hold, attain, or be considered for a specified military rank.
  • D. militaryRank chosen
    Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
  • E. hasMilitaryAuthority
    Indicates that one entity possesses formal power or command to direct, control, or make decisions over the military activities or forces of 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_69c687ee50048190aa151765bef16193 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6c308a08881908501c862b3029321 completed March 27, 2026, 5:48 p.m.
PD Predicate disambiguation batch_69c6ad024860819084b9b535b136ede6 completed March 27, 2026, 4:14 p.m.
Created at: March 27, 2026, 1:59 p.m.