Triple
T22346465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyohashi |
E552402
|
entity |
| Predicate | localSpecialtyFood |
P17971
|
FINISHED |
| Object | Toyohashi curry udon |
—
|
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: Toyohashi curry udon | Statement: [Toyohashi, localSpecialtyFood, Toyohashi curry udon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localSpecialtyFood Context triple: [Toyohashi, localSpecialtyFood, Toyohashi curry udon]
-
A.
hasSpecialtyFood
chosen
Indicates that an entity offers, serves, or is associated with a particular type of specialty food.
-
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.
alsoEats
Indicates that an entity consumes something in addition to another item or items it already eats.
-
E.
traditionalFoodBase
Indicates that one entity serves as the primary ingredient, staple, or foundational component of a traditional food associated with 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157981c0881909ac74d68b99075c2 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.