Triple
T1646979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clayton Hall tram stop |
E35603
|
entity |
| Predicate | openedForPassengerService |
P990
|
FINISHED |
| Object | 2013-02-11 |
—
|
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-02-11 | Statement: [Clayton Hall tram stop, openedForPassengerService, 2013-02-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForPassengerService Context triple: [Clayton Hall tram stop, openedForPassengerService, 2013-02-11]
-
A.
openedForThroughService
Indicates that an entity has been made accessible or available specifically for use via a through-service connection or route, rather than as a standalone endpoint.
-
B.
closedForPassengers
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
C.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
-
D.
openedForUse
chosen
Indicates that something has been made accessible and available for its intended operation or use.
-
E.
openedToRailTraffic
Indicates that a rail line, track, or related infrastructure has begun operating and is officially available for use by train traffic.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaa0fbe984819084f8daee81ca9b67 |
completed | March 6, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69a907ce4dd881909168a1e99505d4ec |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.