Triple
T8012794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand River Transit |
E186533
|
entity |
| Predicate | hasNumberOfRoutes |
P29564
|
FINISHED |
| Object | dozens of bus 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: dozens of bus routes | Statement: [Grand River Transit, hasNumberOfRoutes, dozens of bus routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfRoutes Context triple: [Grand River Transit, hasNumberOfRoutes, dozens of bus routes]
-
A.
numberOfRoutes
chosen
Indicates the total count of distinct routes or paths associated with a given entity or between specified entities.
-
B.
hasRouteNetwork
Indicates that one entity possesses, is associated with, or is covered by a specific route network connecting multiple locations or paths.
-
C.
hasRouteMaps
Indicates that one entity possesses or provides route maps that describe paths, directions, or connections related to another entity.
-
D.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
E.
hasNotableRoute
Indicates that an entity (such as a transportation service or pathway) includes or is associated with a route that is considered significant, well-known, or otherwise noteworthy.
- 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3d73bf048190ad8066a7e95c34b0 |
completed | March 31, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:19 p.m.