Triple
T2591050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sylvia’s Restaurant |
E58121
|
entity |
| Predicate | hasDishes |
P12772
|
FINISHED |
| Object | fried chicken |
—
|
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: fried chicken | Statement: [Sylvia’s Restaurant, hasDishes, fried chicken]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDishes Context triple: [Sylvia’s Restaurant, hasDishes, fried chicken]
-
A.
servesDish
chosen
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
B.
hasCuisineItem
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
-
C.
hasMealType
Indicates that an entity is associated with a specific category or type of meal (such as breakfast, lunch, or dinner).
-
D.
hasStapleFood
Indicates that an entity’s primary or regularly consumed basic food item is another specified entity.
-
E.
hasCharacterDining
Indicates that an entity offers or includes dining experiences where guests can eat while interacting with costumed characters.
- 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd40075f08190b760cb41c1417169 |
completed | March 7, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.