Triple
T5493699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottingham to Skegness |
E123761
|
entity |
| Predicate | terminusTypeAtSkegness |
P9111
|
FINISHED |
| Object | seaside resort terminus |
—
|
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 terminus | Statement: [Nottingham to Skegness, terminusTypeAtSkegness, seaside resort terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusTypeAtSkegness Context triple: [Nottingham to Skegness, terminusTypeAtSkegness, seaside resort terminus]
-
A.
terminusType
chosen
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
-
B.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
C.
terminusInland
Indicates that something ends, concludes, or has its final point within an inland area rather than at a coast or shoreline.
-
D.
terminusCoastal
Indicates that the endpoint or terminus of something (e.g., a route, line, or feature) is located on or directly adjacent to a coast.
-
E.
terminusJunction
Indicates a relationship where a route, line, or path ends at a junction point that serves as its terminal connection.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9281a0148190bb7a8dae9c991b9c |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a8df6481908d1643f7342fe6f0 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.