Triple
T25097312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mutual Recognition Arrangement of the CIPM |
E628624
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | metrology agreement |
C27841
|
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: metrology agreement Context triple: [Mutual Recognition Arrangement of the CIPM, instanceOf, metrology agreement]
-
A.
measurement standardization treaty
chosen
A measurement standardization treaty is an international agreement that establishes and harmonizes common units, definitions, and procedures for measurements to ensure consistency and comparability across participating countries.
-
B.
metrology committee
A metrology committee is a group of experts responsible for establishing, maintaining, and overseeing measurement standards, procedures, and quality assurance within an organization or regulatory context.
-
C.
metrology document
A metrology document is a formal record that defines, specifies, or reports measurement methods, standards, procedures, and results to ensure accuracy, traceability, and consistency in measurement activities.
-
D.
metrology instrument
A metrology instrument is a precision device used to measure and quantify physical properties or dimensions to ensure accuracy, consistency, and compliance with specified standards.
-
E.
General Conference on Weights and Measures
The General Conference on Weights and Measures is an international diplomatic organization that oversees the global standardization and evolution of the International System of Units (SI) and other measurement standards.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:25 a.m.