Triple
T6728852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester–Blackpool North line |
E153583
|
entity |
| Predicate | destinationTypeAtTerminus |
P9111
|
FINISHED |
| Object | seaside resort |
—
|
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: seaside resort | Statement: [Manchester–Blackpool North line, destinationTypeAtTerminus, seaside resort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destinationTypeAtTerminus Context triple: [Manchester–Blackpool North line, destinationTypeAtTerminus, seaside resort]
-
A.
terminusType
chosen
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
-
B.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
-
C.
terminusDirection
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
D.
hasPassengerTerminalFunction
Indicates that something serves the role or performs the function of a passenger terminal, supporting the handling and movement of passengers.
-
E.
railroadTerminusFor
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
- 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_69c6880bdd68819097de8b6099992682 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d08e8a2c8190ae4e8d8c039be7ce |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:08 p.m.