Triple
T11682165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decatur Street |
E277642
|
entity |
| Predicate | hasCuisineTypeAvailable |
P59511
|
FINISHED |
| Object | Creole |
—
|
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: Creole | Statement: [Decatur Street, hasCuisineTypeAvailable, Creole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCuisineTypeAvailable Context triple: [Decatur Street, hasCuisineTypeAvailable, Creole]
-
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.
haveCuisine
chosen
Indicates that an entity (such as a restaurant or place) offers, serves, or is associated with a particular type or style of cuisine.
-
D.
offersCuisine
Indicates that one entity provides or serves a particular type or style of cuisine to others.
-
E.
hasCuisineRecognition
Indicates that an entity has received formal recognition, awards, or notable acknowledgment specifically for its cuisine.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a462bb2881909238107d34c0a28d |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.