Triple
T770775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berne Convention for the Protection of Literary and Artistic Works |
E16275
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international copyright treaty |
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: international copyright treaty Context triple: [Berne Convention for the Protection of Literary and Artistic Works, instanceOf, international copyright treaty]
-
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.
article of an international treaty
An article of an international treaty is a distinct, numbered provision that sets out specific rights, obligations, definitions, or procedures agreed upon by the treaty’s parties.
-
C.
international standard
An international standard is an agreed-upon set of rules, guidelines, or specifications established by recognized global bodies to ensure compatibility, safety, and quality across countries and industries.
-
D.
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.
-
E.
international legal regime
An international legal regime is a structured set of principles, norms, rules, and decision-making procedures agreed upon by states and other actors to govern behavior and cooperation in a specific issue-area of international relations.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.