Triple
T23779418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ternopil bus station |
E587768
|
entity |
| Predicate | primaryBusStationOf |
P81938
|
FINISHED |
| Object | Ternopil |
—
|
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: Ternopil | Statement: [Ternopil bus station, primaryBusStationOf, Ternopil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBusStationOf Context triple: [Ternopil bus station, primaryBusStationOf, Ternopil]
-
A.
isMainBusStationFor
chosen
Indicates that one bus station serves as the primary or central station for a particular area, network, or service.
-
B.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
-
C.
isPublicTransportStation
Indicates that a location functions as a station or stop used by public transportation services such as buses, trains, trams, or subways.
-
D.
transportationFacility
Indicates that one entity is a facility or location used for the transportation or transit of people or goods in relation to another entity.
-
E.
publicTransitStop
Indicates that a location serves as a designated stop or station where public transit vehicles (such as buses, trains, or trams) pick up and drop off passengers.
- 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c62ad61c8190a552e88bce2bad1c |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.