Triple
T35112990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASTM C535 |
E1013347
|
entity |
| Predicate | testOutput |
P58414
|
FINISHED |
| Object | percentage loss of aggregate mass |
—
|
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: percentage loss of aggregate mass | Statement: [ASTM C535, testOutput, percentage loss of aggregate mass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testOutput Context triple: [ASTM C535, testOutput, percentage loss of aggregate mass]
-
A.
outputOf
Indicates that one entity is the result or product generated by the processing, operation, or behavior of another entity.
-
B.
testResult
chosen
Indicates that an entity has produced a specific outcome or value when subjected to a particular test or evaluation.
-
C.
testResultDisplay
Indicates how the outcome of a test is presented or shown to a viewer or system.
-
D.
outputIs
Indicates that one entity functions as the result, product, or outcome produced by another entity or process.
-
E.
outputExpected
Indicates that a particular output is anticipated or required as the result of a given input, process, or condition.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.