Triple

T31423335
Position Surface form Disambiguated ID Type / Status
Subject Thrippunithura E801591 entity
Predicate hasTemple P1191 FINISHED
Object Thrikkakkara Siva Temple
Thrikkakkara Siva Temple is a prominent Hindu temple dedicated to Lord Shiva located near Thrippunithura in the Ernakulam district of Kerala, India.
E2080285 NE 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: Thrikkakkara Siva Temple | Statement: [Thrippunithura, hasTemple, Thrikkakkara Siva Temple]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Thrikkakkara Siva Temple
Triple: [Thrippunithura, hasTemple, Thrikkakkara Siva Temple]
Generated description
Thrikkakkara Siva Temple is a prominent Hindu temple dedicated to Lord Shiva located near Thrippunithura in the Ernakulam district of Kerala, India.

Provenance (5 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_69f348c26f048190b4adadd71b4596c5 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a0beb2cc8190bda62c76d1fce5cc completed May 3, 2026, 1:11 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36ae29efc88190881f2acc5df6de85 completed June 20, 2026, 3:13 p.m.
NEDg Description generation batch_6a36aed66c20819091ea25f3d7c531e9 completed June 20, 2026, 3:16 p.m.
NED2 Entity disambiguation (via description) batch_6a36af6a16688190bb1feb2a972f3945 completed June 20, 2026, 3:19 p.m.
Created at: April 30, 2026, 8:50 p.m.