Triple

T13942939
Position Surface form Disambiguated ID Type / Status
Subject Dharmapuri district E335301 entity
Predicate hasCity P316 FINISHED
Object Dharmapuri E335301 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: Dharmapuri | Statement: [Dharmapuri district, hasCity, Dharmapuri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dharmapuri
Context triple: [Dharmapuri district, hasCity, Dharmapuri]
  • A. Dharapuram
    Dharapuram is a historic town and regional commercial center in the Tiruppur district of Tamil Nadu, India, situated within the Kongu Nadu region.
  • B. Dharmapuri district chosen
    Dharmapuri district is an administrative region in the Indian state of Tamil Nadu known for its natural landscapes, including prominent waterfalls and forested areas.
  • C. Ariyalur
    Ariyalur is a town in Tamil Nadu, India, known for its rich limestone deposits, cement industries, and significant archaeological and fossil findings.
  • D. Ramachandrapuram
    Ramachandrapuram is a town in the Indian state of Andhra Pradesh, known as a local commercial and administrative center in the East Godavari region.
  • E. Gandhipuram
    Gandhipuram is a major commercial and transportation hub in Coimbatore, Tamil Nadu, known for its busy markets, shopping centers, and connectivity.
  • 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_69d81c6081b88190b53e317c3370c8fe completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2e0f6f3c8190a64058b732b0ac52 completed April 14, 2026, 12:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd3cfd550c81909ad487d3d7d7c313 completed May 8, 2026, 1:31 a.m.
Created at: April 9, 2026, 10:17 p.m.