Triple
T14669495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kotturpuram |
E344470
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Saidapet |
E338896
|
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: Saidapet | Statement: [Kotturpuram, locatedNear, Saidapet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saidapet Context triple: [Kotturpuram, locatedNear, Saidapet]
-
A.
Saidapet
chosen
Saidapet is a prominent residential and commercial neighborhood in Chennai, India, known for its busy transport hub and proximity to key administrative and educational institutions.
-
B.
Velachery
Velachery is a major residential and commercial neighborhood in south Chennai, India, known as a key transport hub and IT corridor gateway.
-
C.
Tambaram
Tambaram is a suburban area of Chennai in Tamil Nadu, India, known as an important residential, educational, and transport hub.
-
D.
Mylapore
Mylapore is a historic neighborhood in Chennai, India, known for its ancient temples, cultural heritage, and traditional South Indian character.
-
E.
T. Nagar
T. Nagar is a major commercial and residential neighborhood in Chennai, India, best known as one of the city’s busiest shopping districts for textiles and jewelry.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54ef2908190b189ced65eec434a |
completed | April 14, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe38857068819085e0d62829302abd |
completed | May 8, 2026, 7:24 p.m. |
Created at: April 10, 2026, 1:27 a.m.