Triple
T12924024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Base 27 |
E309195
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Strategic Support Force unit |
C2497
|
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: Strategic Support Force unit Context triple: [Base 27, instanceOf, Strategic Support Force unit]
-
A.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
B.
military unit component
A military unit component is an individual sub-unit or element, such as a squad, platoon, or company, that combines with others to form a larger organized military force.
-
C.
Japan Ground Self-Defense Force unit
A Japan Ground Self-Defense Force unit is an organized, mission-specific formation of personnel and equipment within Japan’s land-based military, structured to conduct defense, security, and support operations under national and international mandates.
-
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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:42 p.m.