Triple
T38597375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganesh Temple, Ranthambore Fort |
E934116
|
entity |
| Predicate | devoteesOfferings |
P30751
|
FINISHED |
| Object | sweets |
—
|
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: sweets | Statement: [Ganesh Temple, Ranthambore Fort, devoteesOfferings, sweets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devoteesOfferings Context triple: [Ganesh Temple, Ranthambore Fort, devoteesOfferings, sweets]
-
A.
hasVotiveOfferings
Indicates that an entity possesses or is associated with votive offerings dedicated or presented in a religious or ritual context.
-
B.
offersPrasadam
Indicates that one entity provides or distributes consecrated food (prasadam) to another entity.
-
C.
worshipersOffer
chosen
Indicates that worshipers present or dedicate offerings to a deity, sacred figure, or religious object.
-
D.
receivesOfferingsOf
Indicates that one entity is the recipient of offerings, tributes, or gifts presented by another entity.
-
E.
receivesDevoteesFrom
Indicates that an entity (such as a place, person, or institution) is the destination to which devotees come or are directed from another 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.