Triple
T3901859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States customary units |
E90512
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial and US customary measurement system |
C5975
|
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: imperial and US customary measurement system Context triple: [United States customary units, instanceOf, imperial and US customary measurement system]
-
A.
imperial system
chosen
The imperial system is a traditional system of measurement that uses units such as inches, feet, yards, and miles for length, and ounces, pounds, and tons for weight, primarily in the United States and a few other countries.
-
B.
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.
-
C.
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.
-
D.
scientific measurement scale
A scientific measurement scale is a standardized system or continuum used to assign numerical or categorical values to observed phenomena, enabling consistent quantification, comparison, and analysis in scientific research.
-
E.
electromagnetic unit system
An electromagnetic unit system is a coherent set of units specifically defined to measure electromagnetic quantities such as charge, current, electric and magnetic fields, and related derived quantities.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.