Triple

T17299637
Position Surface form Disambiguated ID Type / Status
Subject Daund Junction E420006 entity
Predicate connectsTo P845 FINISHED
Object Solapur E149644 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: Solapur | Statement: [Daund Junction, connectsTo, Solapur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Solapur
Context triple: [Daund Junction, connectsTo, Solapur]
  • A. Solapur chosen
    Solapur is a prominent city in southwestern Maharashtra, India, known for its textile industry, religious sites, and cultural significance to Marathi-speaking people.
  • B. Bhopal
    Bhopal is the capital city of the Indian state of Madhya Pradesh, known for its historic lakes, administrative importance, and the site of the 1984 industrial disaster.
  • C. Indore
    Indore is a major commercial and educational hub in central India, known for its vibrant markets, food culture, and rapidly growing urban infrastructure.
  • D. Nashik
    Nashik is a historic city in the Indian state of Maharashtra, known for its religious significance in Hinduism and as a major center of wine production.
  • E. Indiranagar
    Indiranagar is a prominent residential and commercial neighborhood in eastern Bengaluru, known for its upscale eateries, pubs, and shopping streets.
  • 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_69d886db32608190a61e18862c5a8af6 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e438f8efb481908b56172c7f749b62 completed April 19, 2026, 2:07 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0180da5b808190857c51aaa2e85339 completed May 11, 2026, 7:10 a.m.
Created at: April 10, 2026, 5:41 a.m.