Triple
T28279226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stourbridge Junction |
E713092
|
entity |
| Predicate | hasPeakTimeServicesTo |
P136908
|
FINISHED |
| Object | Birmingham Snow Hill |
—
|
NE NERFINISHED |
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: Birmingham Snow Hill | Statement: [Stourbridge Junction, hasPeakTimeServicesTo, Birmingham Snow Hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeakTimeServicesTo Context triple: [Stourbridge Junction, hasPeakTimeServicesTo, Birmingham Snow Hill]
-
A.
hasPeakServiceType
Indicates that an entity is associated with a specific type or category of service provided during peak periods.
-
B.
hasPeakHourService
Indicates that a service operates or is available during designated peak or high-demand hours.
-
C.
hasPeakHourFunction
Indicates that something performs a specific role or behavior during peak hours of activity or usage.
-
D.
hasServiceTime
Indicates that an entity is associated with a specific duration or schedule during which a service is provided.
-
E.
hasPeakServicePattern
chosen
Indicates that there is a specific service pattern or schedule that applies during peak (busiest) operating periods for the related 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 27, 2026, 11:21 p.m.