Triple
T14882492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Northland |
E350033
|
entity |
| Predicate | isPublicTransportOperator |
P34619
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ontario Northland, isPublicTransportOperator, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPublicTransportOperator Context triple: [Ontario Northland, isPublicTransportOperator, true]
-
A.
publicTransportOperatorFor
Indicates that one entity operates or manages public transportation services for another entity or area.
-
B.
hasBusOperator
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
-
C.
isPublicTransport
Indicates that the entity functions as a mode or instance of transportation that is available for use by the general public, typically operating on fixed routes or schedules.
-
D.
hasPublicTransportAgency
Indicates that a place or transport system is served, managed, or overseen by a specific public transportation agency.
-
E.
transportOperator
chosen
Indicates that an entity is responsible for operating or managing the transportation of people or goods between locations.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e7c0e48190af2d68a71130585c |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:56 a.m.