Triple
T34473808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SWB RailRiders |
E884976
|
entity |
| Predicate | yearRenamedRailRiders |
P179401
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [SWB RailRiders, yearRenamedRailRiders, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearRenamedRailRiders Context triple: [SWB RailRiders, yearRenamedRailRiders, 2013]
-
A.
railRidersAreAffiliateOf
Indicates that the rail riders are formally affiliated with, or associated as a subsidiary/partner group of, another organization or entity.
-
B.
reopenedRailwayStationYear
Indicates the year in which a previously closed railway station was reopened to service.
-
C.
railFranchise
Indicates a contractual relationship in which a company is granted the right to operate rail services or manage rail infrastructure within a specified area or route.
-
D.
isTouristRailway
Indicates that a railway is primarily operated for tourism or leisure purposes rather than as a regular public transport service.
-
E.
railHead
Indicates a relationship where one location serves as the terminus or primary endpoint of a railway line for another location or transport link.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720cc1bfc8190a16118e3af8e9316 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71fb0172c81908f23e95ff16b0dec |
completed | May 3, 2026, 10:13 a.m. |
Created at: May 1, 2026, 2:01 a.m.