Triple

T8179156
Position Surface form Disambiguated ID Type / Status
Subject George Lea E191014 entity
Predicate instanceOf P0 FINISHED
Object special forces commander C449 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 commander
Context triple: [George Lea, instanceOf, special forces commander]
  • A. military special operations command
    A military special operations command is a specialized organizational unit responsible for planning, directing, and executing high-risk, strategically critical missions using elite, highly trained forces.
  • B. 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.
  • C. military officer chosen
    A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
  • D. colonial commander
    A colonial commander is a military leader responsible for overseeing, directing, and maintaining control over armed forces and local governance within a colony on behalf of an imperial power.
  • E. army commander post
    An army commander post is a designated command facility or position from which a military commander directs, coordinates, and controls the operations of assigned forces.
  • 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_69ca82c4538081909404325aa5639483 completed March 30, 2026, 2:03 p.m.
Created at: March 30, 2026, 5:40 p.m.