Triple
T14928820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timiryazevskaya |
E372203
|
entity |
| Predicate | railwayConnectionType |
P55099
|
FINISHED |
| Object | suburban rail |
—
|
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: suburban rail | Statement: [Timiryazevskaya, railwayConnectionType, suburban rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayConnectionType Context triple: [Timiryazevskaya, railwayConnectionType, suburban rail]
-
A.
railConnectionPurpose
Indicates the intended function or goal of a particular rail connection between locations or networks.
-
B.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
C.
railwayConnectsTo
Indicates that one railway line, track, or network is directly linked or joined to another, allowing trains to move between them.
-
D.
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.
-
E.
railwayJunctionFor
Indicates that a location serves as a junction point where multiple railway lines or routes connect or intersect for a given railway network or service.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded634e67881909daec9eaef188d09 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:36 a.m.