Triple
T38185432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASTM C115 |
E1005302
|
entity |
| Predicate | usesPropertyMeasured |
P23071
|
FINISHED |
| Object | specific surface of cement |
—
|
LITERAL FINISHED |
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: specific surface of cement | Statement: [ASTM C115, usesPropertyMeasured, specific surface of cement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPropertyMeasured Context triple: [ASTM C115, usesPropertyMeasured, specific surface of cement]
-
A.
measuredProperty
chosen
Indicates that the subject is a measurement that quantifies or assesses the specified property of an entity.
-
B.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
C.
containsMeasure
Indicates that one entity includes or encompasses a specific measure or quantitative component as part of its content or structure.
-
D.
hasMeasuredParameter
Indicates that an entity has a specific parameter that has been quantitatively measured or recorded.
-
E.
usesMeasureDomain
Indicates that one entity employs or relies on a particular measurement domain or measurement framework as the basis for its values or evaluations.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:29 p.m.