Triple

T19670075
Position Surface form Disambiguated ID Type / Status
Subject Raja Bhoj E472309 entity
Predicate title P38 FINISHED
Object Parameshvara 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: Parameshvara | Statement: [Raja Bhoj, title, Parameshvara]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Parameshvara
Context triple: [Raja Bhoj, title, Parameshvara]
  • A. Parameshvara chosen
    Parameshvara is a divine epithet meaning “Supreme Lord,” commonly used in Indian religious and philosophical traditions to denote the highest, all-powerful deity.
  • B. Rajasinha
    Rajasinha was a royal title borne by monarchs of the Nayakkar dynasty that ruled parts of South India and Sri Lanka.
  • C. Chandradeva
    Chandradeva was a prominent 11th-century ruler who founded and consolidated the power of the Gahadavala dynasty in northern India.
  • D. Chamundaraja
    Chamundaraja was a king of the Chaulukya (Solanki) dynasty in present-day Gujarat, India, known for consolidating and expanding the kingdom established by his predecessor Mularaja.
  • E. Govindachandra
    Govindachandra was a prominent 12th-century Indian king known for consolidating and expanding his realm in northern India and fostering cultural and economic prosperity.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e514f2e08190ba70a4449519d218 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6416b9cf8819096f44e3f9fbf86fa completed April 20, 2026, 3:08 p.m.
Created at: April 10, 2026, 1:45 p.m.