Triple
T27815950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biscuits n’ Gravy |
E702665
|
entity |
| Predicate | hasAssociatedDish |
P12772
|
FINISHED |
| Object | biscuits covered in gravy |
—
|
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: biscuits covered in gravy | Statement: [Biscuits n’ Gravy, hasAssociatedDish, biscuits covered in gravy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedDish Context triple: [Biscuits n’ Gravy, hasAssociatedDish, biscuits covered in gravy]
-
A.
hasDishType
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.
hasCuisineItem
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
-
C.
servesDish
chosen
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
D.
hasOwnDishes
Indicates that an entity possesses or is responsible for its own set of dishes, separate from those of others.
-
E.
hasMainIngredient
Indicates that one entity is the primary or most significant ingredient used to make 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 5:45 p.m.