Triple
T1565203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Srisailam Dam |
E33416
|
entity |
| Predicate | nearReligiousSite |
P29505
|
FINISHED |
| Object | Srisailam temple town |
—
|
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 temple town | Statement: [Srisailam Dam, nearReligiousSite, Srisailam temple town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearReligiousSite Context triple: [Srisailam Dam, nearReligiousSite, Srisailam temple town]
-
A.
hasReligiousSite
Indicates that a location or entity possesses, contains, or is associated with a religious site such as a temple, church, mosque, shrine, or similar place of worship.
-
B.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
C.
hasPlaceOfWorship
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
D.
veneratedAt
Indicates that an entity is honored, revered, or worshipped at a particular place or institution.
-
E.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified place.
- F. None of above. chosen
Provenance (4 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90fccd4b48190a44012888a00af7f |
completed | March 5, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69a907b872f0819096b3df6ad502c63e |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a90fcb8ca48190a9ee50559ba73b22 |
completed | March 5, 2026, 5:08 a.m. |
Created at: March 4, 2026, 7:27 p.m.