Triple
T32868307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapatos Festival |
E840717
|
entity |
| Predicate | hasProductTypeFeatured |
P25185
|
FINISHED |
| Object | leather shoes |
—
|
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: leather shoes | Statement: [Sapatos Festival, hasProductTypeFeatured, leather shoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProductTypeFeatured Context triple: [Sapatos Festival, hasProductTypeFeatured, leather shoes]
-
A.
hasFeatured
Indicates that one entity has prominently included, highlighted, or showcased another entity in a special or notable way.
-
B.
productTypePromoted
Indicates that a particular type or category of product is being actively promoted or highlighted, such as through marketing, placement, or special offers.
-
C.
hasListedProductType
chosen
Indicates that an entity has a product associated with it that is categorized under a specific listed product type.
-
D.
hasProduct
Indicates that an entity possesses, offers, or is associated with a particular product.
-
E.
featuredSetType
Indicates the specific category or type assigned to a featured set within a collection or system.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a012594c27081908c80f0e0e6010290 |
completed | May 11, 2026, 12:40 a.m. |
| PD | Predicate disambiguation | batch_6a01252350548190b1df9edc9e581e91 |
completed | May 11, 2026, 12:38 a.m. |
Created at: May 1, 2026, 1:17 a.m.