Triple
T35062414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASTM C128 |
E1011628
|
entity |
| Predicate | requiresConditioning |
P100
|
FINISHED |
| Object | oven-dry condition of aggregate |
—
|
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: oven-dry condition of aggregate | Statement: [ASTM C128, requiresConditioning, oven-dry condition of aggregate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresConditioning Context triple: [ASTM C128, requiresConditioning, oven-dry condition of aggregate]
-
A.
adjustmentRequirement
Indicates that one entity necessitates a change, modification, or recalibration in another entity or process to meet certain conditions or objectives.
-
B.
requires
chosen
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
C.
requiresCare
Indicates that one entity depends on another to provide care, attention, or maintenance for its proper functioning or well-being.
-
D.
usedCondition
Indicates that one entity is employed or applied under a particular state, requirement, or circumstance defined by another entity.
-
E.
preferredConditions
Indicates the specific circumstances or environmental factors that an entity favors or finds most suitable compared to alternatives.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff8cecbf048190860b9f72b8753f5c |
completed | May 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69ff8c4c39dc8190b5bf35adc1bae7c6 |
completed | May 9, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:01 p.m.