Triple
T16960069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Republic of Germany (for certain constitutional functions) |
E411404
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | constitutional entity |
C230
|
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: constitutional entity Context triple: [Federal Republic of Germany (for certain constitutional functions), instanceOf, constitutional entity]
-
A.
constitutional institution
chosen
A constitutional institution is a formally established body or office whose powers, functions, and structure are defined and limited by a constitution to uphold and operate the fundamental framework of a state.
-
B.
political entity
A political entity is an organized group or jurisdiction, such as a state, nation, or governing body, that holds authority to make and enforce collective decisions over a defined population and territory.
-
C.
state-like entity
A state-like entity is an abstraction that encapsulates a distinct configuration of conditions or behaviors within a system, often determining how the system responds to inputs at a given time.
-
D.
constitutional instrument
A constitutional instrument is a formal legal document or set of provisions that establishes, organizes, or amends the fundamental principles and structures of a state or governing entity.
-
E.
government of a sovereign state
The government of a sovereign state is the organized system of institutions and officials that exercises authority, makes and enforces laws, and conducts public policy on behalf of the state within its territory and in relations with other states.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.