Triple
T15298527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Mountain Transit |
E365724
|
entity |
| Predicate | operatesBusRoutes |
P70721
|
FINISHED |
| Object | local 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: local bus routes | Statement: [Green Mountain Transit, operatesBusRoutes, local bus routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesBusRoutes Context triple: [Green Mountain Transit, operatesBusRoutes, local bus routes]
-
A.
operatedRoutes
chosen
Indicates that an agent (such as a company or organization) runs or manages specific routes, typically providing services along those paths.
-
B.
operatesSchoolBuses
Indicates that an entity is responsible for running or managing the operation of school bus services for transporting students.
-
C.
operatesTransitSystem
Indicates that one entity manages and runs the public transportation network or services for another entity or area.
-
D.
hasBusOperator
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
-
E.
operatedOnRoute
Indicates that a transportation service or vehicle was active and provided service along a specified route.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03686bfb8819080ba0caae652170a |
completed | April 16, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.