Triple
T26830976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortlake railway station |
E675497
|
entity |
| Predicate | typicalOffPeakTrainsPerHourToLondonWaterloo |
P198985
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Mortlake railway station, typicalOffPeakTrainsPerHourToLondonWaterloo, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOffPeakTrainsPerHourToLondonWaterloo Context triple: [Mortlake railway station, typicalOffPeakTrainsPerHourToLondonWaterloo, 8]
-
A.
peakDailyTrains
Indicates the maximum number of trains operating per day on a given route, line, or segment during its busiest period.
-
B.
timeToCentralLondonByTrain
Indicates the amount of time it takes to travel by train from a given location to central London.
-
C.
typicalOffPeakFrequencyToHastings
Indicates how often, during typical off-peak times, a service or connection operates to Hastings.
-
D.
railwayTimeUsage
Indicates how much time is spent using or operating a railway within a given context or period.
-
E.
railwayStationUsage
Indicates how frequently or extensively a railway station is used, such as by measuring passenger numbers, train traffic, or overall activity levels.
- F. None of above. chosen
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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
| PDg | Predicate description generation | batch_69ff1a95b6fc81909331bb03e263b5b9 |
completed | May 9, 2026, 11:29 a.m. |
Created at: April 27, 2026, 5:01 a.m.