Triple
T8908903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Counter Terrorism Command |
E212131
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialist unit |
C25280
|
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: specialist unit Context triple: [Counter Terrorism Command, instanceOf, specialist unit]
-
A.
specialist corps
A specialist corps is a dedicated group of highly trained experts within a larger organization or system, formed to perform complex, technical, or niche tasks that require advanced, domain-specific skills.
-
B.
specialized maritime unit
A specialized maritime unit is a dedicated team within a naval or coast guard organization trained and equipped to conduct specific high-skill missions at sea, such as search and rescue, interdiction, special operations, or environmental protection.
-
C.
specialized liaison unit
A specialized liaison unit is a dedicated team that facilitates communication, coordination, and collaboration between distinct organizations, departments, or stakeholder groups to ensure effective information flow and aligned 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. chosen
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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:55 p.m.