Triple
T21269434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottingham–Skegness line |
E524215
|
entity |
| Predicate | endPointType |
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: [Nottingham–Skegness line, endPointType, seaside resort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endPointType Context triple: [Nottingham–Skegness line, endPointType, seaside resort]
-
A.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
B.
endPointExample
Indicates that something serves as a representative or illustrative instance of a particular endpoint.
-
C.
hasEndpointType
Indicates that an entity has a specific type or classification assigned to one of its endpoints.
-
D.
terminusType
chosen
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
-
E.
endpointFeature
Indicates that a particular feature, capability, or characteristic is associated with, provided by, or available at a specific endpoint.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73651115081908b5083ba818a6bb1 |
completed | April 21, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4:01 p.m.