Triple
T30867993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | central Hunan |
E786255
|
entity |
| Predicate | cuisineRegionOf |
P45120
|
FINISHED |
| Object | Hunan cuisine |
—
|
NE NERFINISHED |
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: Hunan cuisine | Statement: [central Hunan, cuisineRegionOf, Hunan cuisine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cuisineRegionOf Context triple: [central Hunan, cuisineRegionOf, Hunan cuisine]
-
A.
ethnicRegionalBase
Indicates that an entity’s support, identity, or operations are primarily rooted in a specific ethnic group within a particular geographic region.
-
B.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
C.
regionOfCulinaryImportance
chosen
Indicates that a location is recognized for its significant culinary relevance, such as notable food traditions, specialties, or gastronomic culture.
-
D.
culturalRegion
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
-
E.
homeCountryRegion
Indicates the country or broader geographic region that is considered the primary home or origin of an 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691adadf4819083f7fd06ecaab732 |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:47 p.m.