Triple
T10948701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Archive in Freiburg |
E258667
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of the German Federal Archives |
C28606
|
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: branch of the German Federal Archives Context triple: [Military Archive in Freiburg, instanceOf, branch of the German Federal Archives]
-
A.
federal agency of Germany
A federal agency of Germany is a governmental body operating at the national level, responsible for implementing federal laws, policies, and administrative tasks within its designated area of competence.
-
B.
branch of the German Army
A branch of the German Army is a specialized organizational subdivision responsible for a distinct set of military functions, capabilities, and operational roles within the overall land forces structure.
-
C.
branch of the Bundeswehr
A branch of the Bundeswehr is a major organizational component of Germany’s armed forces, such as the Army, Navy, or Air Force, each with distinct roles, capabilities, and responsibilities in national defense.
-
D.
museum building in Germany
A museum building in Germany is a purpose-built or repurposed structure located within German territory that houses, preserves, and publicly exhibits collections of cultural, historical, artistic, or scientific significance.
-
E.
Nazi SS office
A Nazi SS office was an administrative and operational unit of the Schutzstaffel responsible for planning, coordinating, and executing the regime’s ideological, security, and genocidal policies.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:23 p.m.