Triple
T34928755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASTM C188 |
E1007366
|
entity |
| Predicate | measurementUnitContext |
P29841
|
FINISHED |
| Object | SI units |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: SI units | Statement: [ASTM C188, measurementUnitContext, SI units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: measurementUnitContext Context triple: [ASTM C188, measurementUnitContext, SI units]
-
A.
unitOfMeasure
Indicates that one entity specifies the standard unit in which the quantity or value of another entity is measured.
-
B.
unitSystem
chosen
Indicates the system of measurement units (such as metric or imperial) that is used to quantify associated values or attributes.
-
C.
measureType
Indicates the specific kind or category of measurement that characterizes how a quantity or value is assessed.
-
D.
measurementOrganization
Indicates that one entity serves as the organization responsible for performing, managing, or overseeing the measurement of another entity or process.
-
E.
notationUnit
Indicates a relationship where one entity serves as a unit, symbol, or element within a system of notation used to represent information or structure.
- F. None of above.
Provenance (3 batches)
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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.