Triple
T11118784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zollverein congress |
E262963
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intergovernmental assembly |
C9247
|
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: intergovernmental assembly Context triple: [Zollverein congress, instanceOf, intergovernmental assembly]
-
A.
supranational parliamentary assembly
A supranational parliamentary assembly is a representative legislative body composed of delegates from multiple sovereign states, empowered to deliberate, make decisions, and sometimes enact binding rules at a level above the nation-state.
-
B.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
C.
intergovernmental platform
chosen
An intergovernmental platform is a structured forum or mechanism through which multiple governments collaborate, coordinate policies, share information, and make joint decisions on issues of common interest.
-
D.
intergovernmental consensus
Intergovernmental consensus is a collective agreement reached among multiple governments or states, typically through negotiation and compromise, that establishes a shared position or decision on a specific issue.
-
E.
inter-parliamentary organization
An inter-parliamentary organization is a cooperative body composed of members from the legislatures of multiple countries, established to promote dialogue, coordination, and collaboration on shared political, legal, and policy issues.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:28 p.m.