Triple
T38104442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mehandipur Balaji Temple |
E951467
|
entity |
| Predicate | devotionalTextUsed |
P162244
|
FINISHED |
| Object | Hanuman Chalisa |
—
|
NE NERFINISHED |
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: Hanuman Chalisa | Statement: [Mehandipur Balaji Temple, devotionalTextUsed, Hanuman Chalisa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devotionalTextUsed Context triple: [Mehandipur Balaji Temple, devotionalTextUsed, Hanuman Chalisa]
-
A.
devotionalTitleUsedBy
Indicates that a particular devotional or honorific title is used to refer to or address a given entity.
-
B.
devotionalElement
chosen
Indicates a relationship where something serves as or functions as an element used in devotional or religious practice.
-
C.
isDevotional
Indicates that something is intended for or characterized by religious worship, reverence, or spiritual devotion.
-
D.
devotionalDayCommon
Indicates that two or more entities share the same religious or spiritual day of devotion or observance.
-
E.
hasDevotionalForm
Indicates that one entity takes or possesses a devotional expression, format, or mode in relation to another entity or context.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.