Triple
T26275698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malton GO Station |
E660560
|
entity |
| Predicate | connectedToBusOperator |
P14541
|
FINISHED |
| Object | MiWay |
—
|
NE NERFINISHED |
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: MiWay | Statement: [Malton GO Station, connectedToBusOperator, MiWay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToBusOperator Context triple: [Malton GO Station, connectedToBusOperator, MiWay]
-
A.
hasBusOperator
chosen
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
-
B.
publicTransportOperatorFor
Indicates that one entity operates or manages public transportation services for another entity or area.
-
C.
connectsToBusAt
Indicates that one entity has an access or transfer point where it links to a bus service at a specific location or stop.
-
D.
accessByBusFrom
Indicates that one location can be reached from another location using a bus as the mode of transportation.
-
E.
associatedLineOperator
Indicates that an entity is linked to, managed by, or otherwise connected with a specific line operator.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 26, 2026, 9:55 p.m.