Triple
T34682964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Militärpolitische Verwaltung der NVA |
E890667
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | politisches Organ |
C35280
|
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: politisches Organ Context triple: [Militärpolitische Verwaltung der NVA, instanceOf, politisches Organ]
-
A.
organ of a political movement
chosen
An organ of a political movement is a structured entity—such as a committee, publication, or media outlet—formally tasked with expressing, implementing, or coordinating the movement’s policies, strategies, and communications.
-
B.
political organization
A political organization is a structured group of individuals who collectively pursue specific political goals, such as influencing public policy, gaining or maintaining power, or representing particular interests within a political system.
-
C.
organ of parliament
An organ of parliament is a formally established body or component within a parliamentary system, such as committees, chambers, or leadership offices, that performs specific legislative, oversight, or administrative functions.
-
D.
organizational body of a political party
An organizational body of a political party is a structured group within the party responsible for coordinating activities, making decisions, and implementing policies at a specific level or in a particular functional area.
-
E.
political party
A political party is an organized group of people who share common political ideals and policy goals and work together to gain and exercise governmental power through elections and public influence.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.