Triple
T7188775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CGPM resolutions |
E167634
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international standard-setting decision |
C1803
|
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 standard-setting decision Context triple: [CGPM resolutions, instanceOf, international standard-setting decision]
-
A.
international standard
chosen
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.
ILO standard-setting instrument
An ILO standard-setting instrument is an international legal tool—such as a convention, recommendation, or protocol—adopted by the International Labour Organization to establish norms and guidelines on labor and social policy issues for member states.
-
C.
standards-setting organization
A standards-setting organization is an entity that develops, maintains, and promotes agreed-upon technical, professional, or procedural norms to ensure compatibility, quality, and interoperability across industries or sectors.
-
D.
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.
-
E.
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.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:50 p.m.