Triple
T21158927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life Savers, Inc. |
E521383
|
entity |
| Predicate | productTexture |
P31484
|
FINISHED |
| Object | hard candy |
—
|
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: hard candy | Statement: [Life Savers, Inc., productTexture, hard candy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productTexture Context triple: [Life Savers, Inc., productTexture, hard candy]
-
A.
texture
Indicates the surface quality or feel of an entity as perceived by touch or appearance, such as being smooth, rough, soft, or coarse.
-
B.
imageMaterial
Indicates that one entity serves as the material or physical medium from which the image entity is composed or rendered.
-
C.
textureCharacteristicInFugue
Indicates that a specified texture characteristic is present or manifested within a particular fugue.
-
D.
typicalTexture
chosen
Indicates the usual or characteristic surface feel or consistency that is commonly associated with an entity.
-
E.
materialDepicted
Indicates that a work or representation visually portrays or includes a particular material as part of its subject.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7252e9ef481908f4904c535f3da8b |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.