Triple
T9716176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungerford railway station |
E235146
|
entity |
| Predicate | hasPassengerInformationServices |
P17090
|
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: [Hungerford railway station, hasPassengerInformationServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassengerInformationServices Context triple: [Hungerford railway station, hasPassengerInformationServices, yes]
-
A.
hasPassengerInformationSystem
chosen
Indicates that an entity is equipped with a system that provides information to passengers, such as schedules, announcements, or travel updates.
-
B.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
-
C.
hasPassengerAirlineService
Indicates that a location or facility is served by scheduled passenger airline flights.
-
D.
usedForPassengerInformation
Indicates that something serves the purpose of providing information to passengers.
-
E.
hasPassengerOnlyService
Indicates that the service provided involves only the transportation of passengers, with no freight or cargo component.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e0bb82081908e21a646f4de1a61 |
completed | April 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:20 p.m.