Triple
T28062660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilmot, Ontario |
E709155
|
entity |
| Predicate | NithRiverFlowsThrough |
P86882
|
FINISHED |
| Object | New Hamburg, Ontario |
—
|
NE NERFINISHED |
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: New Hamburg, Ontario | Statement: [Wilmot, Ontario, NithRiverFlowsThrough, New Hamburg, Ontario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NithRiverFlowsThrough Context triple: [Wilmot, Ontario, NithRiverFlowsThrough, New Hamburg, Ontario]
-
A.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
B.
isOnlyNavigableRiverOf
Indicates that one river is the sole river that can be navigated within a specified area or context.
-
C.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
D.
isWatercourseOf
chosen
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
E.
useRiverSystems
Indicates that an entity utilizes or manages river systems for a particular purpose or function.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64018804c81909397f6bcf1ab0dea |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f637120c008190b2b5adf46f022e48 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:40 p.m.