Triple
T23114765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First South Yorkshire |
E576718
|
entity |
| Predicate | operatesBusRouteType |
P70721
|
FINISHED |
| Object | urban routes |
—
|
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: urban routes | Statement: [First South Yorkshire, operatesBusRouteType, urban routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesBusRouteType Context triple: [First South Yorkshire, operatesBusRouteType, urban routes]
-
A.
operatesInterurbanBusServices
Indicates that an entity runs or manages bus transportation services operating between different towns or cities within a region.
-
B.
operatedRoutes
chosen
Indicates that an agent (such as a company or organization) runs or manages specific routes, typically providing services along those paths.
-
C.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
D.
busSystemName
Indicates that a bus system is identified or referred to by a specific name.
-
E.
operatesTransitSystem
Indicates that one entity manages and runs the public transportation network or services for another entity or area.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e11e9dc819093c569f388ffd46b |
completed | April 29, 2026, 4:50 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:59 p.m.