Triple
T38410049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taste of Hamburg-er festival |
E901448
|
entity |
| Predicate | foodTypeServed |
P48322
|
FINISHED |
| Object | hamburgers |
—
|
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: hamburgers | Statement: [Taste of Hamburg-er festival, foodTypeServed, hamburgers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foodTypeServed Context triple: [Taste of Hamburg-er festival, foodTypeServed, hamburgers]
-
A.
servesType
chosen
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
B.
isTypicallyServedFor
Indicates that one item is most commonly or customarily served as a meal or course for the other (e.g., a dish typically served for breakfast, lunch, or dinner).
-
C.
foodOfferedTo
Indicates that some food is presented or made available by one entity for another entity to receive or consume.
-
D.
foodService
Indicates that one entity provides, manages, or is responsible for supplying food or meal-related services to another entity.
-
E.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
- 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.