Triple
T35174908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASTM C40 |
E1015668
|
entity |
| Predicate | appliesToEndUse |
P199401
|
FINISHED |
| Object | concrete |
—
|
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: concrete | Statement: [ASTM C40, appliesToEndUse, concrete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToEndUse Context triple: [ASTM C40, appliesToEndUse, concrete]
-
A.
canEndOn
Indicates that one entity is allowed or able to terminate, conclude, or finish with another specified entity or condition.
-
B.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
C.
approximateEndUse
Indicates that something is an estimated or inferred final purpose, application, or consumption context of another entity.
-
D.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
E.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69ff3705e424819090ad7423ceefa506 |
completed | May 9, 2026, 1:30 p.m. |
Created at: May 3, 2026, 4:02 p.m.