Triple
T38299682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanjangud Srikanteshwara Temple |
E1032187
|
entity |
| Predicate | templeTankName |
P46303
|
FINISHED |
| Object | Parashurama Thirtha |
—
|
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: Parashurama Thirtha | Statement: [Nanjangud Srikanteshwara Temple, templeTankName, Parashurama Thirtha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeTankName Context triple: [Nanjangud Srikanteshwara Temple, templeTankName, Parashurama Thirtha]
-
A.
hasTempleTank
chosen
Indicates that a temple includes or is associated with a specific water tank or reservoir used for religious or ritual purposes.
-
B.
sacredTankName
Indicates that an entity has a name identifying it as a sacred or holy water tank or reservoir.
-
C.
templeName
Indicates that an entity is identified by or associated with the name of a temple.
-
D.
templeState
Indicates that a temple is in a particular condition, status, or phase (such as operational, under construction, abandoned, or ceremonial).
-
E.
templeTitleOf
Indicates that one entity is the formal religious or ceremonial title held by another entity within a temple or sacred 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.