Triple

T17958908
Position Surface form Disambiguated ID Type / Status
Subject Viluppuram district E449023 entity
Predicate hasTown P847 FINISHED
Object Viluppuram E343119 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: Viluppuram | Statement: [Viluppuram district, hasTown, Viluppuram]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Viluppuram
Context triple: [Viluppuram district, hasTown, Viluppuram]
  • A. Villupuram chosen
    Villupuram is a major town and transport hub in the Indian state of Tamil Nadu, known for its important railway junction linking routes across the region.
  • B. Perambalur
    Perambalur is a town and district headquarters in the Indian state of Tamil Nadu, known for its agricultural economy and historical temples.
  • C. Chengalpattu
    Chengalpattu is a town and administrative center in the Indian state of Tamil Nadu, located southwest of Chennai and known as a growing suburban and industrial hub.
  • D. Pattukkottai
    Pattukkottai is a town in the Thanjavur district of Tamil Nadu, India, known for its agricultural economy and role as a regional commercial center.
  • 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 (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_69d8b9f8cca8819099836916c56b7c95 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4b130b7a081908542a3bc6dab5842 completed April 19, 2026, 10:40 a.m.
NED1 Entity disambiguation (via context triple) batch_6a035657374081908bc447b4cad5e5d4 completed May 12, 2026, 4:33 p.m.
Created at: April 10, 2026, 10:22 a.m.