Triple
T36996305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berkswell railway station |
E915236
|
entity |
| Predicate | hasTicketOfficeOpeningHours |
P17011
|
FINISHED |
| Object | part-time |
—
|
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: part-time | Statement: [Berkswell railway station, hasTicketOfficeOpeningHours, part-time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketOfficeOpeningHours Context triple: [Berkswell railway station, hasTicketOfficeOpeningHours, part-time]
-
A.
openingHoursCharacteristic
chosen
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
B.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
C.
busStationOpened
Indicates that a bus station began operating or was officially opened at a specific time or event.
-
D.
hasBookingOffice
Indicates that one entity maintains or is associated with a booking office where reservations or ticketing services are handled for it.
-
E.
plannedOpeningPeriod
Indicates the time span during which something is scheduled or intended to open or begin operating.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.