Triple
T8579090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertford North railway station |
E203121
|
entity |
| Predicate | hasNationalRailService |
P82952
|
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: [Hertford North railway station, hasNationalRailService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNationalRailService Context triple: [Hertford North railway station, hasNationalRailService, yes]
-
A.
hasNationalRailCategory
Indicates that an entity is assigned a specific classification or category within a national rail system.
-
B.
hasNationalRailPlatforms
Indicates that an entity possesses one or more platforms used by the national rail network for train services.
-
C.
isNationalRailwaySystemOf
Indicates that one entity functions as the official national railway system serving and operating within the territory of another entity.
-
D.
isInNationalRailTimetable
Indicates that something is included as an entry or service in the official National Rail timetable.
-
E.
railwayTypeServed
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
- 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea9a0708819084cb8b8d84017864 |
completed | March 31, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69cbd11b13108190b07f8f161425a585 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:22 p.m.