Triple
T6719980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heart of Wessex Line |
E153368
|
entity |
| Predicate | railNetworkSector |
P68241
|
FINISHED |
| Object | regional 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: regional rail | Statement: [Heart of Wessex Line, railNetworkSector, regional rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railNetworkSector Context triple: [Heart of Wessex Line, railNetworkSector, regional rail]
-
A.
railwayNetworkSector
chosen
Indicates a relationship where something is classified as, or associated with, a specific sector or segment of a railway network.
-
B.
railNetworkRole
Indicates the specific function or responsibility an entity has within a rail network system.
-
C.
railNetworkCenter
Indicates that a location functions as a central hub or focal point within a rail transportation network.
-
D.
railNetworkSide
Indicates on which side of a rail network (e.g., left or right relative to a reference direction) an entity is located or associated.
-
E.
railroadNetwork
Indicates a relationship where locations are connected as part of the same system of railway lines and infrastructure used for train transport.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d137084881908e04ee6b2bd45585 |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.