Triple
T1148370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algonquin Provincial Park |
E23618
|
entity |
| Predicate | hasWaterRouteType |
P17791
|
FINISHED |
| Object | canoe 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: canoe routes | Statement: [Algonquin Provincial Park, hasWaterRouteType, canoe routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterRouteType Context triple: [Algonquin Provincial Park, hasWaterRouteType, canoe routes]
-
A.
transportsWaterTo
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
-
B.
hasWaterwayRole
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
-
C.
waterTransport
Indicates the movement or conveyance of something from one place to another via water-based means such as rivers, seas, or other aquatic routes.
-
D.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
E.
waterwayClass
chosen
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.