Triple
T18737819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Padmavathi Ammavari Temple |
E458209
|
entity |
| Predicate | sacredTankUsedFor |
P46303
|
FINISHED |
| Object | ritual baths |
—
|
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: ritual baths | Statement: [Sri Padmavathi Ammavari Temple, sacredTankUsedFor, ritual baths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacredTankUsedFor Context triple: [Sri Padmavathi Ammavari Temple, sacredTankUsedFor, ritual baths]
-
A.
sacredTankName
Indicates that an entity has a name identifying it as a sacred or holy water tank or reservoir.
-
B.
usedSacredVesselsFrom
Indicates that one entity made use of sacred or consecrated vessels that originated from or belonged to another entity.
-
C.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
D.
hasTempleTank
chosen
Indicates that a temple includes or is associated with a specific water tank or reservoir used for religious or ritual purposes.
-
E.
sacredElement
Indicates that one entity is regarded as holy, revered, or spiritually significant within the religious or cultural context of the other 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5768b80ac8190bc05628d64f86fc9 |
completed | April 20, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.