Triple
T13548483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | former Cambridge and St Ives railway line |
E323577
|
entity |
| Predicate | successorTransportMode |
P110294
|
FINISHED |
| Object | guided bus |
—
|
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: guided bus | Statement: [former Cambridge and St Ives railway line, successorTransportMode, guided bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorTransportMode Context triple: [former Cambridge and St Ives railway line, successorTransportMode, guided bus]
-
A.
successorTractionType
Indicates that one traction type directly follows or replaces another in a sequence or evolution of traction systems.
-
B.
successorRollingStockType
Indicates that one rolling stock type directly follows and replaces another in operational succession.
-
C.
successorStation
Indicates that one station directly follows another in a sequence, such as along a transit line or route.
-
D.
publicTransitMode
Indicates the type of public transportation (e.g., bus, train, subway) used or associated with a given trip or segment.
-
E.
successorHighway
Indicates that one highway directly follows or continues from another in a sequence or route.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbbb8c77dc8190b7bd803b5e168d23 |
completed | April 12, 2026, 3:34 p.m. |
Created at: April 9, 2026, 9:45 p.m.