Triple
T37877654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of Soul Food |
E944776
|
entity |
| Predicate | associatedWithDishType |
P84496
|
FINISHED |
| Object | comfort food |
—
|
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: comfort food | Statement: [Queen of Soul Food, associatedWithDishType, comfort food]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithDishType Context triple: [Queen of Soul Food, associatedWithDishType, comfort food]
-
A.
hasDishType
chosen
Indicates that an item (such as a food or menu entry) is classified as belonging to a particular type of dish (e.g., appetizer, main course, dessert).
-
B.
servedTogetherWith
Indicates that two entities were provided, offered, or used at the same time as part of the same service, event, or context.
-
C.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
D.
isTypicallyEatenWith
Indicates that one item is commonly consumed together with another as part of the same eating occasion or dish.
-
E.
referencesDish
Indicates that one entity cites, mentions, or points to a specific dish as a reference.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.