Triple
T18522112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kudrovo |
E452610
|
entity |
| Predicate | commuterFlowDirection |
P24810
|
FINISHED |
| Object | towards Saint Petersburg |
—
|
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: towards Saint Petersburg | Statement: [Kudrovo, commuterFlowDirection, towards Saint Petersburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commuterFlowDirection Context triple: [Kudrovo, commuterFlowDirection, towards Saint Petersburg]
-
A.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
B.
transportDirection
chosen
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
C.
weekdayPeakDirectionService
Indicates that the service operates primarily during weekday peak travel periods in a specific direction.
-
D.
railwayTrafficDirection
Indicates the customary side of the track on which trains are operated or expected to run within a given railway system or segment.
-
E.
hasCommuterTraffic
Indicates that there is regular, recurring traffic flow associated with people traveling between their homes and places of work or study.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5338e6e188190a41a4ee12c1ad330 |
completed | April 19, 2026, 7:57 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.