Triple

T25963200
Position Surface form Disambiguated ID Type / Status
Subject Temple City of India E645596 entity
Predicate hasNotableTemple P48433 FINISHED
Object Ananta Vasudeva Temple
Ananta Vasudeva Temple is a historic Hindu shrine in Bhubaneswar, Odisha, renowned for its dedication to Lord Krishna and its distinctive Kalinga-style architecture.
E1763072 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: Ananta Vasudeva Temple | Statement: [Temple City of India, hasNotableTemple, Ananta Vasudeva 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: Ananta Vasudeva Temple
Triple: [Temple City of India, hasNotableTemple, Ananta Vasudeva Temple]
Generated description
Ananta Vasudeva Temple is a historic Hindu shrine in Bhubaneswar, Odisha, renowned for its dedication to Lord Krishna and its distinctive Kalinga-style architecture.

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_69e77e85efc08190997da7fcf98bd300 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f604c7ec9081908f026c897dcfedc4 completed May 2, 2026, 2:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1262405cb08190a3421cb53c97993d completed May 24, 2026, 2:28 a.m.
NEDg Description generation batch_6a126440683881909b462092139a79cf completed May 24, 2026, 2:36 a.m.
NED2 Entity disambiguation (via description) batch_6a1264a5d7748190902dbe10317c00a8 completed May 24, 2026, 2:38 a.m.
Created at: April 22, 2026, 8:47 a.m.