Triple
T36691786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prussian–American Treaty of Amity and Commerce |
E905975
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | treaty of amity and commerce |
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: treaty of amity and commerce Context triple: [Prussian–American Treaty of Amity and Commerce, instanceOf, treaty of amity and commerce]
-
A.
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.
-
B.
treaty port concession
A treaty port concession is a designated area within a host country’s port where, under unequal treaty arrangements, foreign powers exercise special commercial, legal, and administrative privileges distinct from local jurisdiction.
-
C.
bilateral diplomatic agreement
A bilateral diplomatic agreement is a formal, negotiated arrangement between two sovereign states that defines mutual rights, obligations, and cooperative actions in specific areas of shared interest.
-
D.
treaty system
A treaty system is a structured network of formal agreements between states or entities that collectively govern their mutual rights, obligations, and interactions over specific issues or regions.
-
E.
treaty annex
A treaty annex is a supplementary document attached to a main treaty that provides detailed provisions, technical specifications, or additional terms that form an integral part of the overall agreement.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.