Triple

T6054151
Position Surface form Disambiguated ID Type / Status
Subject Sapta Puri E134866 entity
Predicate hasMember P10 FINISHED
Object Mathura E26469 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: Mathura | Statement: [Sapta Puri, hasMember, Mathura]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mathura
Context triple: [Sapta Puri, hasMember, Mathura]
  • A. Mathura chosen
    Mathura is an ancient city in northern India revered in Hinduism as the birthplace of Lord Krishna and a major pilgrimage center.
  • B. Shrivardhan
    Shrivardhan is a coastal town in Maharashtra, India, historically notable as the birthplace of Balaji Vishwanath, the first Peshwa of the Maratha Empire.
  • C. Jagadhri
    Jagadhri is a city in the Indian state of Haryana, known historically for its metal and brass industries and forming a twin city with Yamunanagar.
  • D. Ujjayini
    Ujjayini is the ancient name of the historic Indian city of Ujjain, a major cultural and religious center known for its prominence in Hindu tradition and astronomy.
  • E. Bharuch
    Bharuch is an ancient port city in the Indian state of Gujarat, historically significant as a major trading hub on the banks of the Narmada River.
  • 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_69c00877b6d4819096b0e163728b73a3 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c05708fda48190ad3d1860969ebb6a completed March 22, 2026, 8:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69c1357027388190beef9b9d9f5e37f6 completed March 23, 2026, 12:43 p.m.
Created at: March 22, 2026, 4:09 p.m.