Triple
T37405296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Buses route 381 |
E929110
|
entity |
| Predicate | hasRealTimeInformationProvidedBy |
—
|
GENERATED |
| Object | TfL Countdown system |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRealTimeInformationProvidedBy Context triple: [London Buses route 381, hasRealTimeInformationProvidedBy, TfL Countdown system]
-
A.
hasRealTimeInformation
Indicates that up-to-date, continuously refreshed information is available about the related entity or event.
-
B.
supportsRealTime
chosen
Indicates that one entity provides or enables real-time operation, processing, or interaction for another entity or process.
-
C.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
D.
hasTimetableInformationDisplays
Indicates that an entity is equipped with displays that present timetable or schedule information.
-
E.
hasTimeIndication
Indicates that something includes, specifies, or is associated with a particular time-related indication (such as a timestamp, time period, or temporal marker).
- F. None of above.
Provenance (1 batch)
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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.