Triple
T29953597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNER Class V2 |
E760834
|
entity |
| Predicate | notableRouteUse |
P83751
|
FINISHED |
| Object | East Coast Main Line |
E40678
|
NE 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: East Coast Main Line | Statement: [LNER Class V2, notableRouteUse, East Coast Main Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRouteUse Context triple: [LNER Class V2, notableRouteUse, East Coast Main Line]
-
A.
notableRouteType
Indicates that a route is particularly significant or well-known for a specific type or category (e.g., scenic, historic, commercial).
-
B.
notableUse
Indicates that something is prominently or famously used by a particular entity, context, or for a specific purpose.
-
C.
notableRouteFeature
Indicates that a route is associated with a distinctive or significant feature, such as a landmark, characteristic terrain, or other notable aspect along its path.
-
D.
usedRoutes
chosen
Indicates that an entity has utilized or traveled along specific routes.
-
E.
notableLocationUse
Indicates that a location is notably used for a particular purpose, activity, or function associated with the subject.
- F. None of above.
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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2714358bc881909e6d91db90885c64 |
completed | June 8, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 6:26 p.m.