Triple
T34347884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cocoa Pebbles |
E881485
|
entity |
| Predicate | isChocolateVariantOf |
P178899
|
FINISHED |
| Object | Fruity Pebbles |
—
|
NE NERFINISHED |
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: Fruity Pebbles | Statement: [Cocoa Pebbles, isChocolateVariantOf, Fruity Pebbles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isChocolateVariantOf Context triple: [Cocoa Pebbles, isChocolateVariantOf, Fruity Pebbles]
-
A.
isFlavouredVariantOf
Indicates that one item is a version of another that has been modified or distinguished specifically by added or altered flavor characteristics.
-
B.
isSoftDrinkVariantOf
Indicates that one soft drink is a specific version, flavor, or formulation derived from or based on another soft drink.
-
C.
isOfficialFlavorOf
Indicates that one item is formally recognized or designated as an official flavor associated with another entity (such as a brand, product line, or event).
-
D.
typicalFlavor
Indicates that something characteristically has or is associated with a particular flavor.
-
E.
hasSugarFreeVariant
Indicates that an item has a corresponding version or option that is formulated without sugar.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71782422c81908196d5e4a610cb1a |
completed | May 3, 2026, 9:38 a.m. |
Created at: May 1, 2026, 1:58 a.m.