Triple
T35108495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whatcom Transportation Authority |
E1013217
|
entity |
| Predicate | hasScheduleInformation |
P87953
|
FINISHED |
| Object | published timetables |
—
|
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: published timetables | Statement: [Whatcom Transportation Authority, hasScheduleInformation, published timetables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScheduleInformation Context triple: [Whatcom Transportation Authority, hasScheduleInformation, published timetables]
-
A.
hasSchedulePage
Indicates that an entity is associated with a dedicated page or resource that presents its schedule or timetable.
-
B.
hasPerformanceSchedule
Indicates that an entity has an associated timetable or plan specifying when its performances or shows are scheduled to occur.
-
C.
hasTimetableInformation
chosen
Indicates that an entity provides or is associated with detailed schedule or timetable information for another entity or service.
-
D.
hasScheduleType
Indicates that an entity is associated with a particular kind or category of schedule (e.g., recurring, one-time, or specific scheduling pattern).
-
E.
containsSchedule
Indicates that one entity includes or holds a schedule associated with another entity or activity.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 3, 2026, 4:01 p.m.