Triple
T35849653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamas |
E1036314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | undercover unit |
C53620
|
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: undercover unit Context triple: [Yamas, instanceOf, undercover unit]
-
A.
special weapons and tactics unit
A special weapons and tactics unit is a highly trained law enforcement team equipped and organized to handle high-risk operations such as hostage rescues, armed standoffs, and counterterrorism incidents beyond the capabilities of regular police patrols.
-
B.
SS special unit
A highly trained, elite military or paramilitary formation within the SS, organized for specialized missions such as reconnaissance, sabotage, counterinsurgency, or high-risk combat operations.
-
C.
security and intelligence unit
chosen
A security and intelligence unit is an organized group responsible for gathering, analyzing, and acting on information to prevent threats and protect people, assets, and critical operations.
-
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 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.