Triple
T26674061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOS |
E672410
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II military support organization |
C13448
|
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: World War II military support organization Context triple: [SOS, instanceOf, World War II military support organization]
-
A.
World War II military formation
A World War II military formation is an organized grouping of military units—such as divisions, corps, or armies—structured and deployed by a nation’s armed forces during the Second World War to conduct coordinated combat and support operations.
-
B.
World War II-era agency
A World War II-era agency is an organization, typically governmental or intergovernmental, established during the Second World War to coordinate military, economic, intelligence, or civilian efforts in support of the war.
-
C.
World War II civilian group
A World War II civilian group is a collective of non-military individuals organized for purposes such as resistance, support, survival, or collaboration within the social, political, and economic upheavals of the war.
-
D.
World War II military role
A World War II military role represents a specific set of duties, responsibilities, and functions performed by individuals or units within the armed forces of nations involved in the conflict between 1939 and 1945.
-
E.
military support organization
chosen
A military support organization is an entity that provides logistical, administrative, technical, and welfare services to enable and sustain the effective operation of armed forces.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:15 a.m.