Triple

T5604619
Position Surface form Disambiguated ID Type / Status
Subject Leningradsky Prospekt E147201 entity
Predicate hasTrafficCharacteristic P29452 FINISHED
Object heavy traffic 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: heavy traffic | Statement: [Leningradsky Prospekt, hasTrafficCharacteristic, heavy traffic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTrafficCharacteristic
Context triple: [Leningradsky Prospekt, hasTrafficCharacteristic, heavy traffic]
  • A. hasTrafficPattern chosen
    Indicates that there is a characteristic or recurring flow of traffic associated with an entity, such as its typical volume, direction, or timing of movement.
  • B. hasTrafficRegime
    Indicates that a specified traffic control or regulatory system applies to a given road, area, or transport context.
  • C. hasTrafficFunction
    Indicates that an entity performs, supports, or is assigned a specific function or role related to traffic management or control.
  • D. hasTruckTraffic
    Indicates that there is truck-related vehicular movement or flow occurring on or through a specified location or route.
  • E. hasTrafficDirection
    Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
  • 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_69c0090500f881908374285baf0ac46f completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c020f9408481908cf006074c726301 completed March 22, 2026, 5:03 p.m.
PD Predicate disambiguation batch_69c01b1890ec8190b9e6fa488792e4d4 completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:39 p.m.