Triple

T7016329
Position Surface form Disambiguated ID Type / Status
Subject Hooghly district E162707 entity
Predicate containsTown P847 FINISHED
Object Pandua E191146 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: Pandua | Statement: [Hooghly district, containsTown, Pandua]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pandua
Context triple: [Hooghly district, containsTown, Pandua]
  • A. Pandua chosen
    Pandua is a historic city in present-day West Bengal, India, that served as an important political and cultural center during the medieval Bengal Sultanate.
  • B. Bhailsa
    Bhailsa is the former historical name of Vidisha, an ancient city in the central Indian state of Madhya Pradesh known for its rich archaeological and cultural heritage.
  • C. Agrai
    Agrai was an ancient deme of Attica in Greece, known as the site of the Lesser Mysteries associated with the Eleusinian cult.
  • D. Birpur
    Birpur is a town in the Supaul district of Bihar, India, situated near the Kosi River and known for its proximity to the major Kosi Barrage.
  • E. Mahoba
    Mahoba is a historic town in Uttar Pradesh, India, renowned for its role as a prominent center of power and culture in the Bundelkhand region, especially under the Chandela rulers.
  • 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_69c6885a127c8190867b059bdccf13ff completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e1d43e948190843f1cef3ce2004e completed March 27, 2026, 8 p.m.
NED1 Entity disambiguation (via context triple) batch_69c76a5655d48190a2df556f63add35d completed March 28, 2026, 5:42 a.m.
Created at: March 27, 2026, 2:34 p.m.