Triple
T7614268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brick Lane |
E172320
|
entity |
| Predicate | isKnownForCuisine |
P45120
|
FINISHED |
| Object | Bangladeshi 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: Bangladeshi cuisine | Statement: [Brick Lane, isKnownForCuisine, Bangladeshi cuisine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKnownForCuisine Context triple: [Brick Lane, isKnownForCuisine, Bangladeshi cuisine]
-
A.
haveCuisine
Indicates that an entity (such as a restaurant or place) offers, serves, or is associated with a particular type or style of cuisine.
-
B.
cuisineType
Indicates the type or style of food associated with an entity, such as a restaurant or dish.
-
C.
isNationalDishOf
Indicates that a particular food is officially or culturally recognized as the national dish of a specific country or region.
-
D.
regionOfCulinaryImportance
chosen
Indicates that a location is recognized for its significant culinary relevance, such as notable food traditions, specialties, or gastronomic culture.
-
E.
cuisine
Indicates the type or style of food traditionally associated with or served by an entity (such as a restaurant or region).
- 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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa418ef081908fd17ff367520995 |
completed | March 27, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:55 p.m.