Triple
T7360867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congress of Berlin |
E169742
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international treaty conference |
C69
|
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: international treaty conference Context triple: [Congress of Berlin, instanceOf, international treaty conference]
-
A.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
B.
diplomatic conference
chosen
A diplomatic conference is a formal gathering of representatives from different states or international organizations convened to negotiate agreements, resolve disputes, or discuss issues of mutual concern.
-
C.
international political forum
An international political forum is a structured platform where representatives from multiple countries convene to discuss, negotiate, and coordinate on global political, economic, and security issues.
-
D.
international diplomatic document
An international diplomatic document is a formal written instrument exchanged between states or international organizations to record, communicate, or formalize agreements, positions, or understandings in the conduct of foreign relations.
-
E.
international political declaration
An international political declaration is a formal, non-binding statement adopted by states or international bodies that articulates shared political intentions, principles, or commitments on global or regional 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:06 p.m.