Triple
T10196303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Star |
E238170
|
entity |
| Predicate | typicalSoleMaterial |
P92636
|
FINISHED |
| Object | rubber |
—
|
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: rubber | Statement: [One Star, typicalSoleMaterial, rubber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSoleMaterial Context triple: [One Star, typicalSoleMaterial, rubber]
-
A.
soleType
Indicates the specific kind or design category of a sole associated with an item (such as footwear or a similar object).
-
B.
traditionalFootwear
Indicates that the relationship involves footwear that is characteristic of, or historically associated with, a particular culture, region, or tradition.
-
C.
typicalFabric
Indicates that something is made from or associated with a fabric material that is standard or characteristic for its type.
-
D.
hasEyelets
Indicates that an object possesses one or more eyelets (small holes or rings typically used for threading or fastening).
-
E.
footType
Indicates the specific kind or classification of feet that an entity possesses or is characterized by.
- 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_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. |
| PDg | Predicate description generation | batch_69cd7edc6cf081909d95859d880a4059 |
completed | April 1, 2026, 8:23 p.m. |
Created at: March 30, 2026, 9:13 p.m.