Triple
T31436174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratcliffe-on-Soar Power Station |
E801936
|
entity |
| Predicate | connectedToRailNetwork |
P95666
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ratcliffe-on-Soar Power Station, connectedToRailNetwork, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToRailNetwork Context triple: [Ratcliffe-on-Soar Power Station, connectedToRailNetwork, yes]
-
A.
connectsToRailwayNetwork
chosen
Indicates that one entity is physically or functionally linked to a railway network, allowing access or transfer between them.
-
B.
belongsToRailNetwork
Indicates that something is part of, or included within, a specific rail network.
-
C.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
D.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
-
E.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: April 30, 2026, 9:01 p.m.