Triple
T21878767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Marylebone – Stourbridge Junction |
E540221
|
entity |
| Predicate | onRailSystem |
P522
|
FINISHED |
| Object | British railway system |
—
|
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: British railway system | Statement: [London Marylebone – Stourbridge Junction, onRailSystem, British railway system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onRailSystem Context triple: [London Marylebone – Stourbridge Junction, onRailSystem, British railway system]
-
A.
hasRailSystem
chosen
Indicates that an entity possesses or is served by a rail-based transportation system.
-
B.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
-
C.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
D.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
E.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118e42c108190b6308016655c429e |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:03 p.m.