Triple
T30582824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidential Guard |
E778427
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | elite security unit |
C22646
|
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: elite security unit Context triple: [Presidential Guard, instanceOf, elite security unit]
-
A.
elite troops
chosen
Elite troops are highly trained, exceptionally skilled military units selected for their superior physical, mental, and tactical capabilities to perform the most demanding and critical missions.
-
B.
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.
-
C.
security and intelligence unit
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.
security force
A security force is an organized group responsible for protecting people, property, and interests by preventing, detecting, and responding to threats or unlawful activities.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:23 p.m.