Triple
T37838633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omkar Mandhata temple |
E943406
|
entity |
| Predicate | sacredRiverAssociation |
P99325
|
FINISHED |
| Object | Narmada River |
—
|
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: Narmada River | Statement: [Omkar Mandhata temple, sacredRiverAssociation, Narmada River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacredRiverAssociation Context triple: [Omkar Mandhata temple, sacredRiverAssociation, Narmada River]
-
A.
sacredRiver
Indicates that a river is regarded as holy or spiritually significant within a religious or cultural tradition.
-
B.
sacredRiverCult
chosen
Indicates a religious practice or belief system that venerates a river as sacred and centers rituals, worship, or cultic activities around it.
-
C.
sacredRiverNearby
Indicates that there is a sacred river located in close proximity to the referenced entity.
-
D.
sacredHill
Indicates that a hill holds religious or spiritual significance within a belief system or tradition.
-
E.
sacredTree
Indicates that an entity is regarded as a sacred or holy tree within a religious, spiritual, or cultural 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.