Triple
T34745387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASTM C143 |
E1001621
|
entity |
| Predicate | definesSlumpConeHeight |
P197751
|
FINISHED |
| Object | 300 mm |
—
|
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: 300 mm | Statement: [ASTM C143, definesSlumpConeHeight, 300 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesSlumpConeHeight Context triple: [ASTM C143, definesSlumpConeHeight, 300 mm]
-
A.
hasCone
Indicates that one entity possesses, is equipped with, or is characterized by a cone or cone-shaped component.
-
B.
coneLength
Indicates the length measurement of a cone-shaped structure associated with an entity.
-
C.
dimensionOfConesDependsOn
Indicates that the dimensionality of a cone is determined by, or functionally depends on, another specified factor or structure.
-
D.
createdCone
Indicates that an entity has produced or brought into existence a cone-shaped object or structure.
-
E.
shaftHeight
Indicates the vertical extent or length of a shaft from its base to its top.
- F. None of above. chosen
Provenance (4 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69fea5e75a5481908a04d91ee7255ebb |
completed | May 9, 2026, 3:11 a.m. |
Created at: May 3, 2026, 3:59 p.m.