Triple
T37930781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cookham railway station |
E946209
|
entity |
| Predicate | hasWaitingRoomOnPlatform |
P3382
|
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: [Cookham railway station, hasWaitingRoomOnPlatform, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaitingRoomOnPlatform Context triple: [Cookham railway station, hasWaitingRoomOnPlatform, yes]
-
A.
hasWaitingShelterOnPlatform1
Indicates that there is a waiting shelter located on platform 1.
-
B.
hasWaitingShelterOnPlatform2
Indicates that platform 2 is equipped with a shelter or covered waiting area for passengers.
-
C.
hasWaitingArea
chosen
Indicates that an entity provides or includes a designated space where people can wait before receiving a service or proceeding to another area.
-
D.
hasWaitingList
Indicates that there exists a queue or list of entities waiting for access to, or participation in, the referenced resource, service, or opportunity.
-
E.
hasPlatformOn
Indicates that one entity is physically supported by or situated on the surface or structure 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:20 p.m.