Triple
T14098320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orathuppalayam |
E339312
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Karur |
E338524
|
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: Karur | Statement: [Orathuppalayam, nearbyCity, Karur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Karur Context triple: [Orathuppalayam, nearbyCity, Karur]
-
A.
Karur
chosen
Karur is a town in the Indian state of Tamil Nadu known as an important textile, bus body building, and industrial center on the banks of the Amaravathi River.
-
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.
Erode
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.
-
D.
Sholinghur
Sholinghur is a historic town in Tamil Nadu, India, known for its role in 18th-century Anglo-Mysore conflicts and its prominent hilltop temples.
-
E.
Mudukulathur
Mudukulathur is a town in the Ramanathapuram district of Tamil Nadu, India, known for its role as a local administrative and commercial center.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fb926288190a7f0f50d1d585d76 |
completed | April 14, 2026, 3:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe967cea3c81909d9b600501897a41 |
completed | May 9, 2026, 2:05 a.m. |
Created at: April 9, 2026, 10:22 p.m.