Triple

T36406978
Position Surface form Disambiguated ID Type / Status
Subject Hoot E896772 entity
Predicate instanceOf P0 FINISHED
Object special forces operator C63321 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07 
Target class: special forces operator
Context triple: [Hoot, instanceOf, special forces operator]
  • A. special operations forces operator chosen
    A special operations forces operator is a highly trained military professional skilled in conducting covert, high-risk missions that require advanced tactical, technical, and physical capabilities.
  • B. special operations forces officer
    A special operations forces officer is a highly trained military leader who plans, coordinates, and commands small, elite units in complex, high-risk missions often requiring unconventional tactics and specialized skills.
  • C. Delta Force operator
    A Delta Force operator is an elite, highly trained special operations soldier specializing in counterterrorism, direct action, and covert missions requiring exceptional skill, discretion, and adaptability.
  • D. special operations forces unit
    A special operations forces unit is a highly trained, small military team designed to conduct specialized, high-risk missions such as reconnaissance, direct action, counterterrorism, and unconventional warfare, often in politically sensitive or denied environments.
  • E. special forces–type unit
    A special forces–type unit is a highly trained, elite military or paramilitary team specialized in conducting high-risk, precision missions such as reconnaissance, counterterrorism, and unconventional warfare, often behind enemy lines or in politically sensitive environments.
  • F. None of above.

Provenance (1 batch)

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_69f76e53b81081908d3b81860593f38a completed May 3, 2026, 3:48 p.m.
Created at: May 3, 2026, 4:10 p.m.