Triple

T35580191
Position Surface form Disambiguated ID Type / Status
Subject Shivanasamudra E1028198 entity
Predicate nearbyAttraction P3449 FINISHED
Object Somnathpur
Somnathpur is a historic village in Karnataka, India, best known for the exquisitely carved 13th-century Chennakesava Temple, a prime example of Hoysala architecture.
E2184137 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: Somnathpur | Statement: [Shivanasamudra, nearbyAttraction, Somnathpur]
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: Somnathpur
Triple: [Shivanasamudra, nearbyAttraction, Somnathpur]
Generated description
Somnathpur is a historic village in Karnataka, India, best known for the exquisitely carved 13th-century Chennakesava Temple, a prime example of Hoysala 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_69f76e0386688190b931bacdc145938c completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79e826f248190a8b8e9344f3f15fc completed May 3, 2026, 7:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39c3dacd408190a68da9461c0dcf9b completed June 22, 2026, 11:23 p.m.
NEDg Description generation batch_6a39c632b85081909d98a94d5ea33b0a completed June 22, 2026, 11:33 p.m.
NED2 Entity disambiguation (via description) batch_6a39c6bf247081908a7e342f1c421dbf completed June 22, 2026, 11:35 p.m.
Created at: May 3, 2026, 4:04 p.m.