Triple
T6637317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Inverness |
E150489
|
entity |
| Predicate | hasEndpointRole |
P34947
|
FINISHED |
| Object | London as southern 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: London as southern terminus | Statement: [London–Inverness, hasEndpointRole, London as southern terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndpointRole Context triple: [London–Inverness, hasEndpointRole, London as southern terminus]
-
A.
hasEndpointType
Indicates that an entity has a specific type or classification assigned to one of its endpoints.
-
B.
hasEndpointStation
chosen
Indicates that something (such as a route, line, or service) has a specific station as one of its terminal endpoints.
-
C.
isKeyEndpointOf
Indicates that one endpoint in a connection, link, or structure serves as the primary or designated key endpoint of the other.
-
D.
hasEndpointCity
Indicates that a route, connection, or path terminates at a particular city as one of its endpoints.
-
E.
hasServicePatternRole
Indicates that an entity participates in a service pattern with a specific functional role or responsibility within that pattern.
- 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_69c687f0ceb08190bf40807bfc605fa5 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:59 p.m.