Triple
T9052601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSS Deer Team |
E216919
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Office of Strategic Services unit |
C25526
|
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: Office of Strategic Services unit Context triple: [OSS Deer Team, instanceOf, Office of Strategic Services unit]
-
A.
Special Operations Executive agent
A Special Operations Executive agent is a covert operative trained to conduct sabotage, espionage, and support for resistance movements behind enemy lines during wartime.
-
B.
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.
-
C.
CIA directorate
A CIA directorate is a major organizational division within the Central Intelligence Agency responsible for a specific core function such as intelligence analysis, clandestine operations, science and technology, or support services.
-
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.
Japanese military administration unit
A Japanese military administration unit is an organizational entity within Japan’s armed forces responsible for managing logistics, personnel, planning, and support functions necessary to sustain military operations.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:10 p.m.