Triple
T10958381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bukit Bintang |
E258902
|
entity |
| Predicate | cuisineAvailable |
P59511
|
FINISHED |
| Object | Malaysian street food |
—
|
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: Malaysian street food | Statement: [Bukit Bintang, cuisineAvailable, Malaysian street food]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cuisineAvailable Context triple: [Bukit Bintang, cuisineAvailable, Malaysian street food]
-
A.
offersCuisine
Indicates that one entity provides or serves a particular type or style of cuisine to others.
-
B.
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.
-
C.
hasCuisineItem
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
-
D.
alsoEats
Indicates that an entity consumes something in addition to another item or items it already eats.
-
E.
dietaryOptions
Indicates the types of diets or food-related preferences, restrictions, or choices that are applicable to or offered for an 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77126d9288190aa5daf2ba83d731d |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.