Triple
T1140251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Euston – Glasgow |
E23432
|
entity |
| Predicate | hasNightServices |
P9559
|
FINISHED |
| Object | no regular sleeper service |
—
|
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: no regular sleeper service | Statement: [London Euston – Glasgow, hasNightServices, no regular sleeper service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNightServices Context triple: [London Euston – Glasgow, hasNightServices, no regular sleeper service]
-
A.
nightService
chosen
Indicates that a service operates or is available during nighttime hours.
-
B.
nightServicePattern
Indicates that a service or operation follows a specific pattern or schedule that applies only during nighttime hours.
-
C.
weekendService
Indicates that a service, operation, or activity is provided or occurs specifically on weekends.
-
D.
servedByAtNight
Indicates that a service or location is operated, attended to, or provided specifically during nighttime hours.
-
E.
hasAfterHoursSession
Indicates that an entity conducts or participates in a session that takes place outside of regular or standard operating hours.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4b52d48190bec2e7ad1cc8efc0 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.