Triple
T5545407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brussels Revision Act |
E145394
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | revision act of the Paris Convention |
C4085
|
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: revision act of the Paris Convention Context triple: [Brussels Revision Act, instanceOf, revision act of the Paris Convention]
-
A.
act of the Lisbon Agreement
An act of the Lisbon Agreement is a formal revision or amendment instrument adopted by member states that updates, supplements, or replaces provisions of the original Lisbon Agreement on the protection of appellations of origin and their international registration.
-
B.
annex to international agreement
An annex to an international agreement is a supplementary document formally attached to the main treaty that provides detailed provisions, technical specifications, or additional obligations that are integral to and legally binding under the agreement.
-
C.
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.
-
D.
treaty amendment
chosen
A treaty amendment is a formal, negotiated change to an existing international agreement that modifies, adds to, or removes specific obligations or provisions for its parties.
-
E.
chapter of an international treaty
A chapter of an international treaty is a major structural division that groups together related articles and provisions addressing a specific thematic area or subject matter within 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_69c008fb879c81909f5bfa56fadc1d46 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:35 p.m.