Triple

T3310404
Position Surface form Disambiguated ID Type / Status
Subject Sarayu E69557 entity
Predicate flowsThrough P225 FINISHED
Object Ayodhya E26191 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: Ayodhya | Statement: [Sarayu, flowsThrough, Ayodhya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ayodhya
Context triple: [Sarayu, flowsThrough, Ayodhya]
  • A. Ayodhya chosen
    Ayodhya is an ancient city in India revered in Hinduism as the birthplace of Lord Rama and a major pilgrimage site.
  • B. Mathura
    Mathura is an ancient city in northern India revered in Hinduism as the birthplace of Lord Krishna and a major pilgrimage center.
  • C. Agra
    Agra is a historic city in northern India renowned for its Mughal-era architecture, most notably the Taj Mahal and Agra Fort.
  • D. Indraprastha
    Indraprastha is the legendary capital city of the Pandavas in the Indian epic Mahabharata, often identified with the region of present-day Delhi.
  • E. Varanasi
    Varanasi is an ancient city on the banks of the Ganges in northern India, revered as one of Hinduism’s holiest pilgrimage sites and a major center of religious, cultural, and spiritual life.
  • 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_69ad859f218081909458d2cebbf57565 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb0eb6dd08190bab1ce80f417966a completed March 8, 2026, 5:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69b432ee11988190843e4b81500b65ca completed March 13, 2026, 3:53 p.m.
Created at: March 8, 2026, 3:11 p.m.