Triple
T32024464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chepauk–Thiruvallikeni Assembly constituency |
E817780
|
entity |
| Predicate | hasHistoricNeighbourhood |
P51598
|
FINISHED |
| Object | Triplicane |
—
|
NE NERFINISHED |
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: Triplicane | Statement: [Chepauk–Thiruvallikeni Assembly constituency, hasHistoricNeighbourhood, Triplicane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricNeighbourhood Context triple: [Chepauk–Thiruvallikeni Assembly constituency, hasHistoricNeighbourhood, Triplicane]
-
A.
hasHistoricDistrict
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
-
B.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic area.
-
C.
hasHistoricDistrictAssociation
chosen
Indicates a relationship in which an entity is associated with, linked to, or part of a designated historic district.
-
D.
hasHistoricCenterNearby
Indicates that one entity is located close to another entity that serves as a historic center or historically significant core area.
-
E.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
- F. None of above.
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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 1, 2026, 12:17 a.m.