Triple
T33185163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearle Wait |
E849447
|
entity |
| Predicate | productCategoryCreated |
P39888
|
FINISHED |
| Object | gelatin dessert mix |
—
|
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: gelatin dessert mix | Statement: [Pearle Wait, productCategoryCreated, gelatin dessert mix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productCategoryCreated Context triple: [Pearle Wait, productCategoryCreated, gelatin dessert mix]
-
A.
createsCategory
chosen
Indicates that one entity establishes or brings into existence a new category for organizing or classifying other entities.
-
B.
productionCategory
Indicates the classification or type of production process, output, or activity that an entity is associated with.
-
C.
sampleCategory
Indicates that an item or instance belongs to, or is classified under, a particular sample category.
-
D.
publishesCategory
Indicates that an entity (such as a publisher or platform) makes content belonging to a particular category publicly available.
-
E.
introducedCategory
Indicates that an entity is responsible for bringing a particular category into use, recognition, or existence within a given context.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 1, 2026, 1:29 a.m.