Triple
T23991113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurdman station |
E605068
|
entity |
| Predicate | connectsBusRoutesTo |
P136848
|
FINISHED |
| Object | downtown Ottawa |
—
|
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: downtown Ottawa | Statement: [Hurdman station, connectsBusRoutesTo, downtown Ottawa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsBusRoutesTo Context triple: [Hurdman station, connectsBusRoutesTo, downtown Ottawa]
-
A.
connectsToBusAt
chosen
Indicates that one entity has an access or transfer point where it links to a bus service at a specific location or stop.
-
B.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
C.
connectsCityTo
Indicates a relationship in which a route, infrastructure, or link joins one city to another, enabling connection or interaction between them.
-
D.
connectsInlandRoutesTo
Indicates that one entity serves as a link or junction that enables inland transportation routes to reach or connect with another entity.
-
E.
stateRouteConnection
Indicates a relationship where a state-level route connects or links two locations or transportation segments.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38b37648190afb003cded3a7484 |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:37 p.m.