Triple
T18996124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Severomuysky Tunnel |
E464817
|
entity |
| Predicate | belongsToRailNetwork |
P134067
|
FINISHED |
| Object | Russian railway network |
—
|
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: Russian railway network | Statement: [Severomuysky Tunnel, belongsToRailNetwork, Russian railway network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToRailNetwork Context triple: [Severomuysky Tunnel, belongsToRailNetwork, Russian railway network]
-
A.
appliesToRailwayNetwork
Indicates that something is relevant or specifically applicable to a railway network as a whole.
-
B.
connectsToRailwayNetwork
Indicates that one entity is physically or functionally linked to a railway network, allowing access or transfer between them.
-
C.
railNetworkRole
Indicates the specific function or responsibility an entity has within a rail network system.
-
D.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
E.
isRailwayStationInNetwork
Indicates that a railway station belongs to, and is served as part of, a particular railway network.
- F. None of above. chosen
Provenance (4 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6819f8c81908bbf0448baf7e34b |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:01 p.m.