Triple
T27031027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RoadKill Cook-off |
E680916
|
entity |
| Predicate | notableDishStyle |
P73154
|
FINISHED |
| Object | creative preparations of wild game |
—
|
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: creative preparations of wild game | Statement: [RoadKill Cook-off, notableDishStyle, creative preparations of wild game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDishStyle Context triple: [RoadKill Cook-off, notableDishStyle, creative preparations of wild game]
-
A.
foodPreparationStyle
chosen
Indicates the manner or method by which food is prepared, cooked, or processed.
-
B.
knownForDish
Indicates that an entity is recognized or notable for preparing, serving, or being associated with a particular dish.
-
C.
traditionalDish
Indicates that the object is a dish customarily prepared, eaten, or recognized within the subject’s cultural or regional tradition.
-
D.
cuisineType
Indicates the type or style of food associated with an entity, such as a restaurant or dish.
-
E.
cuisineSubtype
Indicates that one cuisine is a more specific subtype or variant within the broader category of another 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
Created at: April 27, 2026, 7:13 a.m.