Triple

T13804293
Position Surface form Disambiguated ID Type / Status
Subject Eastern Uttar Pradesh E331720 entity
Predicate hasMajorCity P316 FINISHED
Object Ballia E429901 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: Ballia | Statement: [Eastern Uttar Pradesh, hasMajorCity, Ballia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ballia
Context triple: [Eastern Uttar Pradesh, hasMajorCity, Ballia]
  • A. Ballia chosen
    Ballia is a city in the eastern part of Uttar Pradesh, India, known for its role in the Indian independence movement and as an administrative, cultural, and commercial center of the surrounding region.
  • B. 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.
  • C. Bharathipura
    Bharathipura is a landmark Kannada novel by U. R. Ananthamurthy that critically explores caste, modernity, and social reform in a South Indian village.
  • D. Kawardha
    Kawardha is a regional dialect of the Chhattisgarhi language spoken in parts of the Indian state of Chhattisgarh.
  • E. Alakapuri
    Alakapuri is the opulent celestial city and capital of the wealth-god Kubera in Hindu mythology.
  • 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_69d81c59f8808190a851bc56afdc55e9 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de026c36108190a7436034a730a261 completed April 14, 2026, 9:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7b08db39c8190a76637b36b77d643 completed May 3, 2026, 8:31 p.m.
Created at: April 9, 2026, 10:12 p.m.