Triple

T37099344
Position Surface form Disambiguated ID Type / Status
Subject Indra III E918655 entity
Predicate successor P78 FINISHED
Object Amoghavarsha II
Amoghavarsha II was a relatively obscure Rashtrakuta ruler of early medieval India who briefly occupied the throne before being succeeded by the more prominent king Indra III.
E2218688 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: Amoghavarsha II | Statement: [Indra III, successor, Amoghavarsha II]
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: Amoghavarsha II
Triple: [Indra III, successor, Amoghavarsha II]
Generated description
Amoghavarsha II was a relatively obscure Rashtrakuta ruler of early medieval India who briefly occupied the throne before being succeeded by the more prominent king Indra III.

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_69f76e9a48bc8190a3947508d8bca408 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fb2fee46548190b60e864c81d6787b completed May 6, 2026, 12:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a4043aa70b481908fcce2b643d6da4f completed June 27, 2026, 9:42 p.m.
NEDg Description generation batch_6a4044244a288190a1594e1b2888f56d completed June 27, 2026, 9:44 p.m.
NED2 Entity disambiguation (via description) batch_6a404599f71c81909f3ba82c2ea8885c completed June 27, 2026, 9:50 p.m.
Created at: May 3, 2026, 4:14 p.m.