Triple
T17353743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto Transit Commission bus routes |
E421877
|
entity |
| Predicate | hasSchedulingFeature |
P52664
|
FINISHED |
| Object | timetabled service |
—
|
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: timetabled service | Statement: [Toronto Transit Commission bus routes, hasSchedulingFeature, timetabled service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSchedulingFeature Context triple: [Toronto Transit Commission bus routes, hasSchedulingFeature, timetabled service]
-
A.
hasPerformanceSchedule
Indicates that an entity has an associated timetable or plan specifying when its performances or shows are scheduled to occur.
-
B.
supportsBackupScheduling
Indicates that an entity provides functionality to configure and manage the timing of backup operations for another entity.
-
C.
schedulingUnit
Indicates a relationship where one entity functions as a unit or block used for organizing, allocating, or managing time or resources in a schedule.
-
D.
usedForScheduling
chosen
Indicates that something is employed to plan, arrange, or coordinate the timing of events, tasks, or activities.
-
E.
hasScheduleType
Indicates that an entity is associated with a particular kind or category of schedule (e.g., recurring, one-time, or specific scheduling 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2e660c81908700aed5c42e9043 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.