Triple

T6240339
Position Surface form Disambiguated ID Type / Status
Subject Chanakya E139582 entity
Predicate associatedWith P37 FINISHED
Object Takshashila E140321 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: Takshashila | Statement: [Chanakya, associatedWith, Takshashila]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Takshashila
Context triple: [Chanakya, associatedWith, Takshashila]
  • A. 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.
  • B. Taxila chosen
    Taxila was an ancient city in present-day Pakistan that served as a major center of learning, trade, and administration in South Asia.
  • C. Hastinapura
    Hastinapura is the ancient royal capital of the Kuru kingdom in Indian epic tradition, serving as the primary political and familial setting of the Mahabharata.
  • D. Medininagar
    Medininagar is a prominent town and administrative center in the Palamu district of the Indian state of Jharkhand.
  • E. Pataliputra
    Pataliputra was an ancient Indian city on the Ganges that served as a major political and cultural center, especially under powerful dynasties like the Maurya and Gupta empires.
  • 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_69c008b1c5088190ae6de2555fc05ad8 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c063067d9c819085a18d9d03939266 completed March 22, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69c243ff29248190abbb748601039f60 completed March 24, 2026, 7:57 a.m.
Created at: March 22, 2026, 4:23 p.m.