Triple

T7306733
Position Surface form Disambiguated ID Type / Status
Subject Nalanda E167991 entity
Predicate locatedNear P294 FINISHED
Object Rajgir E295113 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: Rajgir | Statement: [Nalanda, locatedNear, Rajgir]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rajgir
Context triple: [Nalanda, locatedNear, Rajgir]
  • A. Rajgir chosen
    Rajgir is an ancient town in the Indian state of Bihar, historically significant as a major center for both Buddhism and Jainism and once the capital of the Magadha kingdom.
  • B. Janakpuri
    Janakpuri is a prominent residential and commercial neighborhood in West Delhi, India, known for its planned layout, markets, and metro connectivity.
  • C. Samastipur
    Samastipur is a city in the Indian state of Bihar known as an important railway junction and agricultural trade center in the region.
  • D. Sitamarhi
    Sitamarhi is a town in the Indian state of Bihar, historically associated with the legend of Sita’s birthplace and serving as an important local commercial and cultural center.
  • E. Haringhata
    Haringhata is a town in the Indian state of West Bengal, known for its educational institutions and proximity to Kolkata.
  • 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_69c6888d8e3c81909db79714903baf31 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6ebd7dcf88190b3e66bea327fc63d completed March 27, 2026, 8:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7e56443b08190aee2c26633cdcbed completed March 28, 2026, 2:27 p.m.
Created at: March 27, 2026, 3:01 p.m.