Triple
T17168140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Calvert |
E416658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special forces leader |
C22817
|
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 leader Context triple: [Mike Calvert, instanceOf, special forces leader]
-
A.
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.
-
B.
paramilitary leader
A paramilitary leader is an individual who commands, organizes, and directs a non-regular, often politically motivated armed group that operates with military-style structure, tactics, and discipline outside or alongside official state forces.
-
C.
Military leader
chosen
A military leader is an individual who plans, directs, and coordinates armed forces operations, making strategic and tactical decisions to achieve military objectives while managing and motivating personnel under their command.
-
D.
paratroop commander
A paratroop commander is a military leader responsible for planning, coordinating, and directing airborne infantry operations from deployment through mission completion.
-
E.
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.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:37 a.m.