Triple
T30773778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prospekt Lenina |
E783601
|
entity |
| Predicate | typicalUrbanFunction |
—
|
GENERATED |
| Object | commercial corridor |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUrbanFunction Context triple: [Prospekt Lenina, typicalUrbanFunction, commercial corridor]
-
A.
hasUrbanFunction
chosen
Indicates that an entity serves a specific role or purpose within an urban context, such as providing services, infrastructure, or activities typical of a city environment.
-
B.
refersToUrbanFeature
Indicates that one entity makes reference or points specifically to an urban feature such as a city-related structure, space, or infrastructure element.
-
C.
mainUrbanTerminus
Indicates the primary urban endpoint or central city location where a route, line, or service terminates.
-
D.
hasUrbanDistrictFunction
Indicates that an entity serves the administrative or functional role of an urban district within a larger territorial or governance structure.
-
E.
isUrbanService
Indicates that a service operates within or is specifically intended for an urban area or city environment.
- F. None of above.
Provenance (1 batch)
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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:40 p.m.