Triple
T5355164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Railways Western Region |
E102671
|
entity |
| Predicate | railwayRegionCode |
P31833
|
FINISHED |
| Object | WR |
—
|
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: WR | Statement: [British Railways Western Region, railwayRegionCode, WR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayRegionCode Context triple: [British Railways Western Region, railwayRegionCode, WR]
-
A.
railwayRegion
Indicates a relationship where a railway or rail network is associated with, located in, or administered within a particular geographic region.
-
B.
routeRegion
Indicates that a route is located within, passes through, or is associated with a particular geographic region.
-
C.
railwayDivision
Indicates that one administrative railway division is responsible for, manages, or encompasses another railway unit, line, or area within a rail network.
-
D.
subregionCodeFor
chosen
Indicates that one entity is the code assigned to identify a specific subregion of the other entity.
-
E.
transportationRegion
Indicates that one entity serves as, or is associated with, a geographic region relevant to the transportation activities or coverage of 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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd862dbb008190aef653acddafd38b |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.