Triple
T25784179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thiruchendur Murugan Temple |
E649373
|
entity |
| Predicate | sacredWaterBody |
P160284
|
FINISHED |
| Object | Nazhi Kinaru |
—
|
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: Nazhi Kinaru | Statement: [Thiruchendur Murugan Temple, sacredWaterBody, Nazhi Kinaru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacredWaterBody Context triple: [Thiruchendur Murugan Temple, sacredWaterBody, Nazhi Kinaru]
-
A.
waterBodySourceTradition
Indicates the tradition, belief system, or cultural practice from which the association or significance of a water body originates.
-
B.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
C.
waterbodyUsedFor
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
-
D.
addressesWaterBody
Indicates that an action, plan, or measure is directed toward managing, affecting, or dealing with a specific water body.
-
E.
sacredRiver
Indicates that a river is regarded as holy or spiritually significant within a religious or cultural tradition.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f601f106a08190ad7b4537223dbd8c |
completed | May 2, 2026, 1:53 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 22, 2026, 5:53 a.m.