Triple
T37885013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vertrag vom 31. August 1990 zwischen der Bundesrepublik Deutschland und der Deutschen Demokratischen Republik über die Herstellung der Einheit Deutschlands |
E944972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Einigungsvertrag |
C566
|
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: Einigungsvertrag Context triple: [Vertrag vom 31. August 1990 zwischen der Bundesrepublik Deutschland und der Deutschen Demokratischen Republik über die Herstellung der Einheit Deutschlands, instanceOf, Einigungsvertrag]
-
A.
Handelsbündnis
Ein Handelsbündnis ist ein Zusammenschluss von Staaten oder Organisationen, der durch Abkommen den gegenseitigen Handel erleichtert, fördert und reguliert.
-
B.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
C.
Roman–barbarian treaty
A Roman–barbarian treaty is a formal agreement between the Roman state and a non-Roman tribal group that defines terms of peace, alliance, military service, territorial rights, and mutual obligations.
-
D.
church treaty
A church treaty is a formal agreement between religious authorities and secular powers that defines the rights, privileges, and obligations of the church within a given political or legal framework.
-
E.
non‑aggression pact
A non-aggression pact is a formal agreement between two or more parties in which they commit not to engage in military or hostile actions against each other, typically for a specified period.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.