Triple
T28279208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stourbridge Junction |
E713092
|
entity |
| Predicate | branchLineServiceType |
P105233
|
FINISHED |
| Object | shuttle |
—
|
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: shuttle | Statement: [Stourbridge Junction, branchLineServiceType, shuttle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchLineServiceType Context triple: [Stourbridge Junction, branchLineServiceType, shuttle]
-
A.
branchLine
Indicates a relationship where one line, route, or path diverges from and is subordinate to a main or primary line.
-
B.
branchType
Indicates the specific kind or category of branch that an entity belongs to or is associated with.
-
C.
servedLineType
Indicates the type or category of service line associated with or provided in a given context.
-
D.
servedByLineType
chosen
Indicates that a service, stop, or route is operated or covered by a specific type of transit line.
-
E.
servesLineType
Indicates that a service or entity operates or supports a specific type or category of line (e.g., transport, communication, or utility line).
- 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_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:21 p.m.