Triple
T8957017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Street (Pretoria) |
E213497
|
entity |
| Predicate | hasPublicTransportRoutes |
P34620
|
FINISHED |
| Object | bus |
—
|
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: bus | Statement: [Church Street (Pretoria), hasPublicTransportRoutes, bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicTransportRoutes Context triple: [Church Street (Pretoria), hasPublicTransportRoutes, bus]
-
A.
hasPublicTransitRoute
chosen
Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving the related entities.
-
B.
hasPublicTransitMode
Indicates that a location, route, or service is associated with or supports a specific mode of public transportation (e.g., bus, train, tram).
-
C.
hasPublicTransitFunction
Indicates that something serves a role or provides a service related to public transportation operations or infrastructure.
-
D.
hasPublicTransitProvider
Indicates that a place or region is served by a specific public transit operating organization or agency.
-
E.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6728965881908e9f14aaee0c5a18 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7 p.m.