Triple
T13036886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salem district |
E326583
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Mettur |
E327507
|
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: Mettur | Statement: [Salem district, hasTown, Mettur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mettur Context triple: [Salem district, hasTown, Mettur]
-
A.
Mettur
chosen
Mettur is a town in the Salem district of Tamil Nadu, India, known for its major industrial activities and its proximity to one of the largest dams in the state.
-
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.
Kaniguram
Kaniguram is a historic town in South Waziristan, Pakistan, known as a traditional center of the Ormur (Burki) ethnic community.
-
D.
Palamoor
Palamoor is the historical name of Mahbubnagar, a town and district headquarters in the Indian state of Telangana.
-
E.
Mayilappur
Mayilappur is the traditional Tamil name for Mylapore, a historic and culturally significant neighborhood in Chennai, India.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6cbd12eec81908ad5dae638c2210e |
completed | May 3, 2026, 4:15 a.m. |
Created at: April 9, 2026, 8:55 p.m.