Triple
T8695441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A/RES/63/278 |
E206394
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international instrument |
C743
|
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 instrument Context triple: [A/RES/63/278, instanceOf, international instrument]
-
A.
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.
-
B.
international framework
An international framework is a structured set of principles, rules, and mechanisms agreed upon by multiple countries to guide cooperation, coordination, and decision-making on shared global issues.
-
C.
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.
-
D.
international human rights instrument
chosen
An international human rights instrument is a formal, legally or politically binding document adopted by states or international organizations that defines, codifies, and promotes the protection of fundamental human rights and freedoms across national borders.
-
E.
international conservation instrument
An international conservation instrument is a formal agreement, policy, or legal mechanism among multiple countries designed to protect and sustainably manage biodiversity, ecosystems, or natural resources across national boundaries.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.