Triple
T28784830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEPTA Route 97 |
E726774
|
entity |
| Predicate | schedulingInformationAvailableAt |
P87953
|
FINISHED |
| Object | septa.org |
—
|
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: septa.org | Statement: [SEPTA Route 97, schedulingInformationAvailableAt, septa.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schedulingInformationAvailableAt Context triple: [SEPTA Route 97, schedulingInformationAvailableAt, septa.org]
-
A.
offersSchedule
Indicates that one entity provides or makes available a specific schedule to another entity or for a particular purpose.
-
B.
hasTimetableInformation
chosen
Indicates that an entity provides or is associated with detailed schedule or timetable information for another entity or service.
-
C.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
D.
scheduledDestinationAtTimeOfEvent
Indicates that an entity was planned or expected to be at a specific destination at the time a particular event occurred.
-
E.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:21 a.m.