Triple
T17687252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rakfiskfestivalen in Fagernes |
E440926
|
entity |
| Predicate | focusesOnDishType |
P9865
|
FINISHED |
| Object | fermented trout |
—
|
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: fermented trout | Statement: [Rakfiskfestivalen in Fagernes, focusesOnDishType, fermented trout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnDishType Context triple: [Rakfiskfestivalen in Fagernes, focusesOnDishType, fermented trout]
-
A.
hasDishType
Indicates that an item (such as a food or menu entry) is classified as belonging to a particular type of dish (e.g., appetizer, main course, dessert).
-
B.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
C.
dishType
Indicates the classification of a dish according to its culinary category or role (e.g., appetizer, main course, dessert).
-
D.
feastType
chosen
Indicates the specific kind or category of feast associated with an event or occasion.
-
E.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e470488c4081909b747313ef97b69c |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:03 a.m.