Triple
T17399469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Community Transit |
E423048
|
entity |
| Predicate | usedRouteType |
P64008
|
FINISHED |
| Object | via tunnel buses |
—
|
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: via tunnel buses | Statement: [Community Transit, usedRouteType, via tunnel buses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRouteType Context triple: [Community Transit, usedRouteType, via tunnel buses]
-
A.
usesRoutingType
chosen
Indicates that one entity employs or operates according to a specific routing type or routing method associated with another entity.
-
B.
usedRoutes
Indicates that an entity has utilized or traveled along specific routes.
-
C.
routeTypeAccessed
Indicates that a particular type of route has been accessed or used in some context.
-
D.
usesFormerRouteOf
Indicates that one route, service, or pathway currently follows all or part of the alignment or path that was previously used by another route.
-
E.
primaryRouteType
Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43ac0596481908c400916d5c1b971 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.