Triple

T4910719
Position Surface form Disambiguated ID Type / Status
Subject Special Forces Component Command E110223 entity
Predicate typeOfForcesCommanded P57250 FINISHED
Object special operations forces 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: special operations forces | Statement: [Special Forces Component Command, typeOfForcesCommanded, special operations forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfForcesCommanded
Context triple: [Special Forces Component Command, typeOfForcesCommanded, special operations forces]
  • A. commandedForcesOf
    Indicates that one entity held command authority over the military or armed forces associated with another entity.
  • B. commandingForce2Strength
    Indicates that a commanding force possesses or exerts a particular level or measure of strength.
  • C. commandingForce1Strength
    Indicates that one entity has a certain level or measure of strength in its role as the primary commanding force over another entity or situation.
  • D. USForceType chosen
    Indicates the type or category of U.S. military force involved in a given relationship or action.
  • E. occupationForcesCommandedBy
    Indicates that a particular occupation force is under the command or authority of a specified commander or commanding 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_69bd44132b94819088522d92beaadc78 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6e9acc0c819080b07e2e7924d163 completed March 20, 2026, 3:58 p.m.
PD Predicate disambiguation batch_69bd6c325e188190823836d79934e9bc completed March 20, 2026, 3:48 p.m.
Created at: March 20, 2026, 1:29 p.m.