Triple
T32430494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thiruvanmiyur |
E828706
|
entity |
| Predicate | hasITCorridorAccess |
P5520
|
FINISHED |
| Object | Rajiv Gandhi IT Expressway |
—
|
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: Rajiv Gandhi IT Expressway | Statement: [Thiruvanmiyur, hasITCorridorAccess, Rajiv Gandhi IT Expressway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasITCorridorAccess Context triple: [Thiruvanmiyur, hasITCorridorAccess, Rajiv Gandhi IT Expressway]
-
A.
hasCorridor
chosen
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
B.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
-
C.
hasAccessInfrastructure
Indicates that an entity is equipped with or connected to the physical or technical infrastructure necessary to access a particular service, resource, or network.
-
D.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
-
E.
hasParkAccess
Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2ae4f388190b97bfca23ce5ddcd |
completed | May 3, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:55 a.m.