Triple
T38188658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto–Ottawa |
E1005389
|
entity |
| Predicate | hasBusServiceOperatorType |
P193920
|
FINISHED |
| Object | private intercity bus companies |
—
|
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: private intercity bus companies | Statement: [Toronto–Ottawa, hasBusServiceOperatorType, private intercity bus companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusServiceOperatorType Context triple: [Toronto–Ottawa, hasBusServiceOperatorType, private intercity bus companies]
-
A.
hasBusOperator
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
-
B.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
C.
publicTransportOperatorFor
Indicates that one entity operates or manages public transportation services for another entity or area.
-
D.
hasRailTransportOperator
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
E.
transitSystemTypeOperated
Indicates the type of transit system that an operator runs or manages.
- F. None of above. chosen
Provenance (4 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
| PDg | Predicate description generation | batch_69fd592cc56081908ce456114d407616 |
completed | May 8, 2026, 3:31 a.m. |
Created at: May 3, 2026, 4:29 p.m.