Triple

T18594092
Position Surface form Disambiguated ID Type / Status
Subject Mudukulathur E454445 entity
Predicate hasNearbyUrbanCenter P36605 FINISHED
Object Paramakudi NE NERFINISHED

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: Paramakudi | Statement: [Mudukulathur, hasNearbyUrbanCenter, Paramakudi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paramakudi
Context triple: [Mudukulathur, hasNearbyUrbanCenter, Paramakudi]
  • A. Paramakudi chosen
    Paramakudi is a town in the Indian state of Tamil Nadu known as a regional commercial and transportation hub.
  • B. Poondi
    Poondi is a small village in Tamil Nadu, India, known primarily as a base point for treks and pilgrimages to the nearby Vellingiri Hills.
  • C. Karaikudi
    Karaikudi is a town in Tamil Nadu, India, known as the cultural and commercial center of the Chettinad region, famed for its distinctive cuisine and heritage mansions.
  • D. Navithanveli
    Navithanveli is a village-level settlement located in Sri Lanka’s Eastern Province within the Ampara District.
  • E. Pudukkottai
    Pudukkottai is a historic town and administrative center in Tamil Nadu, India, known for its temples, palaces, and archaeological sites.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d38ae7e081908a98df1251842402 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e545b8d76881909db1539c7150befb completed April 19, 2026, 9:14 p.m.
Created at: April 10, 2026, 11:44 a.m.