Triple
T36199245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max (Where the Wild Things Are) |
E1047212
|
entity |
| Predicate | foodMotif |
P136283
|
FINISHED |
| Object | supper |
—
|
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: supper | Statement: [Max (Where the Wild Things Are), foodMotif, supper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foodMotif Context triple: [Max (Where the Wild Things Are), foodMotif, supper]
-
A.
foodRelatedMotif
chosen
Indicates a recurring theme, symbol, or pattern in which food plays a central role in the relationship or action between entities.
-
B.
foodCulture
Indicates the relationship between a place or group and its characteristic traditions, practices, and preferences surrounding food and eating.
-
C.
foodCustom
Indicates a culturally specific practice, rule, or tradition related to the preparation, serving, or consumption of food.
-
D.
cuisine
Indicates the type or style of food traditionally associated with or served by an entity (such as a restaurant or region).
-
E.
cuisineFeature
Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular cuisine.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.