Triple
T11438803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarangapani Temple |
E271081
|
entity |
| Predicate | hasRatha |
P99300
|
FINISHED |
| Object | temple chariot |
—
|
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: temple chariot | Statement: [Sarangapani Temple, hasRatha, temple chariot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRatha Context triple: [Sarangapani Temple, hasRatha, temple chariot]
-
A.
hasGhat
Indicates that a place or location possesses or is associated with a ghat (a series of steps or landing area leading to a body of water).
-
B.
hasMatha
Indicates a relationship where one entity possesses, is associated with, or is characterized by a specific matha (monastic institution or religious seat).
-
C.
hasRaga
Indicates that something (such as a musical piece, performance, or composition) is associated with or based on a specific raga.
-
D.
hasRind
Indicates that an entity possesses a tough, outer protective layer or skin (a rind).
-
E.
isPancharangaKshetram
Indicates that a temple or sacred site is recognized as one of the Pancharanga Kshetrams, the five traditional holy shrines dedicated to Lord Ranganatha (Vishnu) along the Kaveri river.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8088711ec8190afae9f4d9f2a11ca |
completed | April 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:35 p.m.