Triple
T35470081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orbital Drop Shock Troopers |
E1025184
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNSC special forces unit |
C61189
|
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: UNSC special forces unit Context triple: [Orbital Drop Shock Troopers, instanceOf, UNSC special forces unit]
-
A.
UNSC military personnel
UNSC military personnel are the organized, trained, and equipped members of the United Nations Space Command’s armed forces responsible for conducting space, air, land, and naval operations to defend humanity and its interests.
-
B.
Rebel Alliance military unit
A Rebel Alliance military unit is an organized group of freedom fighters, soldiers, and support personnel operating under the Rebel Alliance command structure to conduct missions against the Galactic Empire.
-
C.
special forces–type unit
chosen
A special forces–type unit is a highly trained, elite military or paramilitary team specialized in conducting high-risk, precision missions such as reconnaissance, counterterrorism, and unconventional warfare, often behind enemy lines or in politically sensitive environments.
-
D.
Marine Corps special operations unit
A Marine Corps special operations unit is an elite, highly trained military formation specializing in direct action, special reconnaissance, and unconventional warfare in maritime and littoral environments.
-
E.
UNSC Marine
A UNSC Marine is a highly trained frontline infantry soldier of the United Nations Space Command, specializing in versatile ground and boarding operations against human and alien threats.
- 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.