Triple
T4172666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilak Bridge, New Delhi |
E86399
|
entity |
| Predicate | isUrbanInfrastructure |
P40290
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tilak Bridge, New Delhi, isUrbanInfrastructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanInfrastructure Context triple: [Tilak Bridge, New Delhi, isUrbanInfrastructure, true]
-
A.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
-
B.
isUrbanRoute
Indicates that a route is located within, passes through, or primarily serves an urban or metropolitan area.
-
C.
isUrbanCenter
Indicates that a place functions as a primary, densely developed hub of population, services, and activities within a region.
-
D.
isPublicInfrastructure
chosen
Indicates that something is part of publicly accessible, collectively used facilities or systems typically provided or regulated by government for common use.
-
E.
isUrbanNeighborhood
Indicates that a given area functions as a neighborhood located within an urban or city environment.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.