Triple
T8245708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DuPont Corian |
E192843
|
entity |
| Predicate | isMoldResistant |
P67874
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [DuPont Corian, isMoldResistant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMoldResistant Context triple: [DuPont Corian, isMoldResistant, true]
-
A.
distanceToMold
Indicates the measured or estimated spatial distance between an entity and a specified mold.
-
B.
isResistant
chosen
Indicates that an entity can withstand, oppose, or is not significantly affected by a specified force, influence, or agent.
-
C.
isNonCombustible
Indicates that the subject does not burn or support combustion under normal conditions.
-
D.
mouldedDepth
Indicates the depth dimension that has been formed or shaped into an object during a moulding process.
-
E.
designedToWithstand
Indicates that something has been intentionally created or engineered to resist, endure, or remain functional under specified conditions, forces, or stresses.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7872f6d481909ea1d3c2aad1a2b1 |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.