Triple
T25096107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 熊本市 |
E628592
|
entity |
| Predicate | 有名な食文化 |
P79219
|
FINISHED |
| Object | 辛子蓮根 |
—
|
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: 辛子蓮根 | Statement: [熊本市, 有名な食文化, 辛子蓮根]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 有名な食文化 Context triple: [熊本市, 有名な食文化, 辛子蓮根]
-
A.
foodCulture
Indicates the relationship between a place or group and its characteristic traditions, practices, and preferences surrounding food and eating.
-
B.
cuisine
Indicates the type or style of food traditionally associated with or served by an entity (such as a restaurant or region).
-
C.
haveDistinctCulinaryTraditions
Indicates that the related entities possess different and distinguishable culinary practices, cuisines, or food-related customs from one another.
-
D.
knownForDish
chosen
Indicates that an entity is recognized or notable for preparing, serving, or being associated with a particular dish.
-
E.
regionOfCulinaryImportance
Indicates that a location is recognized for its significant culinary relevance, such as notable food traditions, specialties, or gastronomic culture.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b9651481908d4d7584717f5c59 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:25 a.m.