Triple
T37383507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scooby Snacks |
E928500
|
entity |
| Predicate | hasMerchandiseVersion |
P200444
|
FINISHED |
| Object | licensed human snack products |
—
|
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: licensed human snack products | Statement: [Scooby Snacks, hasMerchandiseVersion, licensed human snack products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMerchandiseVersion Context triple: [Scooby Snacks, hasMerchandiseVersion, licensed human snack products]
-
A.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
B.
hasExhibitionVersion
Indicates that one entity serves as an exhibition-specific version or variant of another entity.
-
C.
hasMultipleVersions
Indicates that an entity exists in more than one distinct version or revision.
-
D.
hasVersionFor
Indicates that one entity serves as a specific version or variant tailored for another entity.
-
E.
hasVersionCharacteristic
Indicates that one entity is associated with a specific version-related property or feature of another entity.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
| PDg | Predicate description generation | batch_69ff8afe9d5c8190bd5ae434fc2b550b |
completed | May 9, 2026, 7:29 p.m. |
Created at: May 3, 2026, 4:16 p.m.