Triple
T10319407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metre Convention |
E242101
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | measurement standardization treaty |
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: measurement standardization treaty Context triple: [Metre Convention, instanceOf, measurement standardization treaty]
-
A.
international measure
An international measure is a standardized metric, policy, or action adopted across multiple countries to enable consistent comparison, coordination, or regulation on a global scale.
-
B.
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.
-
C.
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.
-
D.
national measurement standards laboratory
A national measurement standards laboratory is an official institution responsible for developing, maintaining, and disseminating a country’s primary measurement standards to ensure accuracy, consistency, and international compatibility of measurements.
-
E.
historical unit of measurement
A historical unit of measurement is a quantity standard once used in a specific culture or period to measure physical properties like length, mass, or volume, but later replaced or standardized in modern systems.
- F. None of above. chosen
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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:49 a.m.