Triple
T16470133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakeside station on Windermere |
E400037
|
entity |
| Predicate | transportModeConnection |
P86086
|
FINISHED |
| Object | rail |
—
|
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: rail | Statement: [Lakeside station on Windermere, transportModeConnection, rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModeConnection Context triple: [Lakeside station on Windermere, transportModeConnection, rail]
-
A.
transportConnectionTo
Indicates a relationship where one entity provides or participates in a means of transportation that connects or leads to another entity.
-
B.
transportModeTo
Indicates the means or mode of transportation used to travel to a specified destination.
-
C.
transportLinkType
Indicates the specific kind of transportation connection or route that exists between two locations or transport nodes.
-
D.
transportModeIntegration
Indicates that different modes of transportation are coordinated or combined to enable seamless or efficient movement within a journey or transport system.
-
E.
transportModePresent
chosen
Indicates that a particular mode of transportation is involved or available in the described context or event.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dcfed6c8190b8dbe4b65b0ab817 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:11 a.m.