Triple

T20150843
Position Surface form Disambiguated ID Type / Status
Subject Alaṅkāraśāstra E491428 entity
Predicate associatedWith P37 FINISHED
Object Daṇḍin 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: Daṇḍin | Statement: [Alaṅkāraśāstra, associatedWith, Daṇḍin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Daṇḍin
Context triple: [Alaṅkāraśāstra, associatedWith, Daṇḍin]
  • A. Daṇḍin chosen
    Daṇḍin was a classical Sanskrit poet and literary theorist, renowned for his influential works on poetics and ornate prose style in early medieval India.
  • B. Dande
    Dande is a town and municipality located in Angola’s Bengo Province.
  • C. Danta
    Danta is a town in the Banaskantha district of Gujarat, India, known for its historical and cultural significance in the region.
  • D. Dashanana
    Dashanana is an epithet of the demon-king Ravana from the Hindu epic Ramayana, highlighting his legendary form with ten heads and immense power.
  • E. Dhamdaha
    Dhamdaha is a town in the Purnia district of Bihar, India, known primarily as a local administrative and market center for the surrounding rural region.
  • 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_69da6265f8f0819080b29c752a574088 completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e667a1c5848190975b17ab07251f8b completed April 20, 2026, 5:51 p.m.
Created at: April 11, 2026, 11:33 p.m.