Triple
T29186461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Govinda’s restaurant or prasadam hall |
E739880
|
entity |
| Predicate | foodOfferedAt |
P63561
|
FINISHED |
| Object | Krishna Balaram Mandir altar |
—
|
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: Krishna Balaram Mandir altar | Statement: [Govinda’s restaurant or prasadam hall, foodOfferedAt, Krishna Balaram Mandir altar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foodOfferedAt Context triple: [Govinda’s restaurant or prasadam hall, foodOfferedAt, Krishna Balaram Mandir altar]
-
A.
foodOfferedTo
Indicates that some food is presented or made available by one entity for another entity to receive or consume.
-
B.
offersFoodInLocation
chosen
Indicates that an entity provides or serves food at a specified location.
-
C.
storesFood
Indicates that one entity keeps or holds food items for future use or consumption.
-
D.
hasFoodOption
Indicates that an entity offers, provides, or includes a particular type of food or dining option.
-
E.
foodCustom
Indicates a culturally specific practice, rule, or tradition related to the preparation, serving, or consumption of food.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6638722fc819098f18314dfa88a6c |
completed | May 2, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, noon