Triple
T5415319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TheBus routes |
E121114
|
entity |
| Predicate | hasScheduleType |
P63521
|
FINISHED |
| Object | fixed-route schedules |
—
|
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: fixed-route schedules | Statement: [TheBus routes, hasScheduleType, fixed-route schedules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScheduleType Context triple: [TheBus routes, hasScheduleType, fixed-route schedules]
-
A.
containsSchedule
Indicates that one entity includes or holds a schedule associated with another entity or activity.
-
B.
hasWorkSchedule
Indicates that an entity is assigned or follows a specific work schedule, defining when they are expected to work.
-
C.
scheduledServiceType
Indicates the type or category of service that has been scheduled between entities (e.g., maintenance, appointment, or delivery).
-
D.
hasActivityType
Indicates the specific kind or category of activity associated with an entity or event.
-
E.
usesScheduleFormat
Indicates that one entity adopts or follows the schedule structure, pattern, or formatting defined by another entity.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87be754c81909c0d0df6216cae46 |
completed | March 20, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8741e8588190863fd5cfb559136d |
completed | March 20, 2026, 5:43 p.m. |
Created at: March 20, 2026, 2:05 p.m.