Triple
T30317477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bai cuisine |
E771094
|
entity |
| Predicate | dish |
P168840
|
FINISHED |
| Object | raw pork slices (shengpi) style dishes |
—
|
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: raw pork slices (shengpi) style dishes | Statement: [Bai cuisine, dish, raw pork slices (shengpi) style dishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dish Context triple: [Bai cuisine, dish, raw pork slices (shengpi) style dishes]
-
A.
dishType
Indicates the classification of a dish according to its culinary category or role (e.g., appetizer, main course, dessert).
-
B.
dishShape
Indicates that one entity has the physical form or contour characterized by the other entity as its shape.
-
C.
dishFamily
Indicates that one dish belongs to the same culinary family or category as another dish, based on shared style, origin, or key characteristics.
-
D.
dishDiameter
Indicates the measurement of how wide a dish is across its center.
-
E.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
- F. None of above. chosen
Provenance (4 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6819505d48190a37f6ce47a34e309 |
completed | May 2, 2026, 10:58 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 7:51 p.m.