Triple
T22478676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham New Street – Nottingham |
E555701
|
entity |
| Predicate | hasCallingPattern |
P148359
|
FINISHED |
| Object | stopping and semi-fast services |
—
|
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: stopping and semi-fast services | Statement: [Birmingham New Street – Nottingham, hasCallingPattern, stopping and semi-fast services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCallingPattern Context triple: [Birmingham New Street – Nottingham, hasCallingPattern, stopping and semi-fast services]
-
A.
hasCallInNumber
Indicates that an entity has an associated telephone number designated for receiving incoming calls.
-
B.
hasCall
Indicates that one entity initiates or participates in a telephone or voice communication with another entity.
-
C.
hasCallLine
Indicates that there is a specific telephone or communication line associated with or used for a particular call.
-
D.
callsTo
Indicates that one entity initiates a call or communication action directed toward another entity.
-
E.
callingStyle
Indicates the manner or convention by which one entity initiates or performs a call or invocation on another entity.
- F. None of above. chosen
Provenance (4 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be653bc8190a2e5c47e38228bfe |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:49 p.m.