Triple
T16308392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Володарский мост |
E395979
|
entity |
| Predicate | имеет полосу движения |
P2128
|
FINISHED |
| Object | автомобильные полосы |
—
|
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: автомобильные полосы | Statement: [Володарский мост, имеет полосу движения, автомобильные полосы]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имеет полосу движения Context triple: [Володарский мост, имеет полосу движения, автомобильные полосы]
-
A.
hasDedicatedLanes
Indicates that specific lanes within a route or roadway are reserved exclusively for a particular type of traffic or use.
-
B.
hasLanes
chosen
Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
-
C.
laneSurface
Indicates the type or condition of the surface that makes up a lane used for travel or traffic.
-
D.
hasEmergencyLane
Indicates that a road, route, or similar thoroughfare includes a designated emergency lane for use by emergency or breakdown situations.
-
E.
hasCarpoolLanes
Indicates that a road, route, or transportation facility includes designated carpool (high-occupancy vehicle) lanes available for use.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288d776808190a7c9918477f07216 |
completed | April 17, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.