Triple
T37901656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Финляндский вокзал |
E945429
|
entity |
| Predicate | обслуживаетПоезда |
P55099
|
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.
trains
Indicates that one entity teaches, instructs, or coaches another entity to develop skills, knowledge, or abilities.
-
B.
maintainsTrainsFor
Indicates that one entity is responsible for servicing, repairing, or otherwise keeping trains operational for another entity.
-
C.
servicesRollingStock
Indicates that an entity provides operational services to or performs work on rolling stock (such as trains or rail vehicles).
-
D.
operatesRailNetworkOf
Indicates that one entity manages and runs the rail network belonging to or associated with another entity.
-
E.
railwayTypeServed
chosen
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.