Triple
T7795900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kongu Nadu |
E180296
|
entity |
| Predicate | hasEconomicCenter |
P1027
|
FINISHED |
| Object | Erode |
E65067
|
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: Erode | Statement: [Kongu Nadu, hasEconomicCenter, Erode]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Erode Context triple: [Kongu Nadu, hasEconomicCenter, Erode]
-
A.
Erode
chosen
Erode is a major city in the South Indian state of Tamil Nadu, known as a textile and turmeric trading hub on the banks of the Kaveri River.
-
B.
Mudukulathur
Mudukulathur is a town in the Ramanathapuram district of Tamil Nadu, India, known for its role as a local administrative and commercial center.
-
C.
Perambalur
Perambalur is a town and district headquarters in the Indian state of Tamil Nadu, known for its agricultural economy and historical temples.
-
D.
Dharapuram
Dharapuram is a historic town and regional commercial center in the Tiruppur district of Tamil Nadu, India, situated within the Kongu Nadu region.
-
E.
Villupuram
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.
- 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_69ca827d22208190b4dc5aa680edcf5d |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cae94c41408190b73e37c0ff2c6628 |
completed | March 30, 2026, 9:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd66d1507c8190a84a69cd0130bb3b |
completed | April 1, 2026, 6:41 p.m. |
Created at: March 30, 2026, 4:31 p.m.