Triple
T159474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kramerbooks & Afterwords Cafe |
E3248
|
entity |
| Predicate | cuisine |
P6863
|
FINISHED |
| Object | American cuisine |
—
|
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: American cuisine | Statement: [Kramerbooks & Afterwords Cafe, cuisine, American cuisine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cuisine Context triple: [Kramerbooks & Afterwords Cafe, cuisine, American cuisine]
-
A.
traditionalCuisine
Indicates that an entity is associated with the customary or historically rooted style of cooking and food preparation characteristic of a particular culture, region, or community.
-
B.
diet
Indicates that an entity regularly consumes a particular type or range of food as its primary source of nutrition.
-
C.
feast
Indicates that an entity participates in or hosts a large, elaborate meal or celebration involving abundant food and communal dining.
-
D.
domesticCup
Indicates that an entity has won or participated in a domestic (national-level) cup competition within its sport or domain.
-
E.
placeOfOrigin
Indicates the location or source from which an entity originally comes or was created.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a25855baf48190a1b63f2e5865d957 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25660c2a48190b4174d5e6da3cb9d |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2580b00988190868ee24c0289cf70 |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.