Triple
T12656977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASTM C618 |
E302309
|
entity |
| Predicate | classifiesMaterial |
P100400
|
FINISHED |
| Object | Class F fly ash |
—
|
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: Class F fly ash | Statement: [ASTM C618, classifiesMaterial, Class F fly ash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classifiesMaterial Context triple: [ASTM C618, classifiesMaterial, Class F fly ash]
-
A.
classificationAccordingTo
chosen
Indicates that an entity is assigned a particular class, type, or category as defined or determined by a specified source, standard, or authority.
-
B.
collectsMaterialType
Indicates that an entity gathers or acquires materials of a specified type.
-
C.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
D.
organizesMaterialType
Indicates that one entity arranges or structures another entity according to a specific type or category of material.
-
E.
classificationIncludes
Indicates that a broader classification category encompasses or contains a specified subclass, member, or element within its scope.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:18 p.m.