Triple
T17306527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John "Soap" MacTavish |
E420178
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special forces operative |
C36640
|
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 operative Context triple: [John "Soap" MacTavish, instanceOf, special forces operative]
-
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.
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.
special operations forces course
A special operations forces course is an intensive training program designed to develop elite military personnel in advanced combat skills, unconventional warfare, and high-risk mission execution.
-
D.
covert operative
chosen
A covert operative is a highly trained individual who conducts secret missions and gathers sensitive information while maintaining a concealed identity and minimizing detection.
-
E.
special operations support unit
A special operations support unit is a specialized organization that provides logistical, intelligence, technical, and operational assistance to special operations forces to enable and sustain their missions.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:43 a.m.