Triple

T10373092
Position Surface form Disambiguated ID Type / Status
Subject Sironcha E244431 entity
Predicate hasNearbyTown P3883 FINISHED
Object Gadchiroli E156021 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: Gadchiroli | Statement: [Sironcha, hasNearbyTown, Gadchiroli]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gadchiroli
Context triple: [Sironcha, hasNearbyTown, Gadchiroli]
  • A. Gadchiroli chosen
    Gadchiroli is a district in the eastern part of Maharashtra, India, known for its dense forests, tribal population, and Naxalite (Maoist) insurgency-affected areas.
  • B. Karamchedu
    Karamchedu is a village in Andhra Pradesh, India, known for its agrarian community and as the site of the 1985 Karamchedu caste violence.
  • C. Sullurpeta
    Sullurpeta is a town in Andhra Pradesh, India, known primarily for its proximity to India’s premier spaceport, the Satish Dhawan Space Centre at Sriharikota.
  • D. Tadipatri
    Tadipatri is a town in the Anantapur district of Andhra Pradesh, India, known for its granite industries and historic temples.
  • E. Nagole
    Nagole is a residential and commercial neighborhood in Hyderabad, India, served as a key terminus and transit hub on the Hyderabad Metro network.
  • 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_69d381b3e328819094b23b8edcd29b5a completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e97f8a148190bb04996132cd464a completed April 7, 2026, 11:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69d90d76fd88819086c61c40216a8932 completed April 10, 2026, 2:47 p.m.
Created at: April 6, 2026, 12:02 p.m.