Triple
T22192858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Bureau for the Protection of Industrial Property |
E548472
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | treaty administrative body |
C2067
|
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 administrative body Context triple: [International Bureau for the Protection of Industrial Property, instanceOf, treaty administrative body]
-
A.
treaty
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.
intergovernmental legal body
chosen
An intergovernmental legal body is an organization formed by multiple governments to develop, interpret, or oversee the implementation of international legal norms, agreements, and dispute-resolution mechanisms.
-
C.
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.
-
D.
civilian administrative body
A civilian administrative body is a non-military organization responsible for managing public affairs, implementing policies, and providing governmental services within a defined jurisdiction.
-
E.
treaty practice
Treaty practice is the body of procedures, behaviors, and interpretive approaches that states and international actors consistently follow in negotiating, applying, and understanding treaties.
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:35 p.m.