Triple

T11201916
Position Surface form Disambiguated ID Type / Status
Subject Tailapa II E265060 entity
Predicate issue P2239 FINISHED
Object Satyashraya E911723 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: Satyashraya | Statement: [Tailapa II, issue, Satyashraya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Satyashraya
Context triple: [Tailapa II, issue, Satyashraya]
  • A. Satyashraya chosen
    Satyashraya was a prominent Western Chalukya ruler of early medieval India, noted for consolidating and expanding the dynasty’s power in the Deccan region.
  • B. Sudarshan
    Sudarshan is a common Indian surname found across various regions and communities in India.
  • C. Priyadarshana
    Priyadarshana is traditionally regarded as one of the children of Mahavira, the 24th Tirthankara in Jainism.
  • D. Dhrishta
    Dhrishta is a figure in Hindu mythology known as one of the sons of Shraddhadeva Manu, associated with the early dynastic lineages of humanity.
  • E. Gunabhadra
    Gunabhadra was a prominent Jain poet and scholar associated with the Rashtrakuta dynasty, known for his significant contributions to medieval Indian religious and literary traditions.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6aa9eb9248190b20211772621b4bc completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8c36c188190bfa4d5f8e6cbbbea completed April 9, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4ad0984e08190af9c8263cc2a079d completed April 19, 2026, 10:23 a.m.
Created at: April 8, 2026, 9:29 p.m.