Triple
T14588072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hosur Road |
E342368
|
entity |
| Predicate | urbanSectionType |
P114961
|
FINISHED |
| Object | six-lane road |
—
|
LITERAL 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: six-lane road | Statement: [Hosur Road, urbanSectionType, six-lane road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanSectionType Context triple: [Hosur Road, urbanSectionType, six-lane road]
-
A.
urbanDistrictType
Indicates the classification of an urban district according to its specific type or category within an administrative or planning system.
-
B.
urbanComponent
Indicates that something functions as a constituent part or element within an urban area or city system.
-
C.
isUrbanSectionOf
Indicates that one area or segment is the part of a larger entity that lies within an urban or city environment.
-
D.
cityDistrictType
Indicates the type or classification of a city district within an urban or administrative structure.
-
E.
urbanDevelopmentType
Indicates the specific category or nature of urban development associated with or applied to an entity (e.g., residential, commercial, mixed-use).
- F. None of above. chosen
Provenance (4 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4237d88819097f3f9a40f5be152 |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:24 a.m.