Triple
T26642216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patala Ganga (Krishna riverfront) |
E668810
|
entity |
| Predicate | sacredWaterBodyFor |
P160284
|
FINISHED |
| Object | Srisailam devotees |
—
|
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: Srisailam devotees | Statement: [Patala Ganga (Krishna riverfront), sacredWaterBodyFor, Srisailam devotees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacredWaterBodyFor Context triple: [Patala Ganga (Krishna riverfront), sacredWaterBodyFor, Srisailam devotees]
-
A.
sacredWaterBody
chosen
Indicates that a water body holds religious or spiritual significance within a belief system or ritual practice.
-
B.
sacredRiverNearby
Indicates that there is a sacred river located in close proximity to the referenced entity.
-
C.
sacredRiver
Indicates that a river is regarded as holy or spiritually significant within a religious or cultural tradition.
-
D.
waterBodySourceTradition
Indicates the tradition, belief system, or cultural practice from which the association or significance of a water body originates.
-
E.
waterbodyUsedFor
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
- 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61632d4908190a3db8fdf80984043 |
completed | May 2, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:29 a.m.