Triple
T3995891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreal bus network |
E87096
|
entity |
| Predicate | hasRouteCategory |
P6300
|
FINISHED |
| Object | 10–199 regular 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: 10–199 regular routes | Statement: [Montreal bus network, hasRouteCategory, 10–199 regular routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteCategory Context triple: [Montreal bus network, hasRouteCategory, 10–199 regular routes]
-
A.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
B.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
C.
hasRouteFeature
Indicates that a route possesses or is associated with a specific characteristic, attribute, or feature.
-
D.
routeCategory
chosen
Indicates the classification or type assigned to a route within a transportation or path network.
-
E.
hasCategoryWithin
Indicates that one category is contained within or is a subcategory of another category.
- 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.