Triple
T10196318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Star |
E238170
|
entity |
| Predicate | typicalInsoleFeature |
P5084
|
FINISHED |
| Object | cushioned insole |
—
|
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: cushioned insole | Statement: [One Star, typicalInsoleFeature, cushioned insole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInsoleFeature Context triple: [One Star, typicalInsoleFeature, cushioned insole]
-
A.
footType
Indicates the specific kind or classification of feet that an entity possesses or is characterized by.
-
B.
soleType
Indicates the specific kind or design category of a sole associated with an item (such as footwear or a similar object).
-
C.
toeShape
Indicates the specific form or contour of an entity’s toe or toe area.
-
D.
designedForComfort
Indicates that something has been intentionally created or configured to enhance physical or psychological ease and reduce discomfort.
-
E.
typicalFeatures
chosen
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
- 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdedcaf6688190938d8e56e29493eb |
completed | April 2, 2026, 4:17 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:13 p.m.