Triple
T1193722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humber River |
E25619
|
entity |
| Predicate | cityWaterwayRole |
P13535
|
FINISHED |
| Object | major natural corridor in Toronto |
—
|
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: major natural corridor in Toronto | Statement: [Humber River, cityWaterwayRole, major natural corridor in Toronto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityWaterwayRole Context triple: [Humber River, cityWaterwayRole, major natural corridor in Toronto]
-
A.
hasWaterwayRole
chosen
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
-
B.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
C.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
D.
waterwayJunction
Indicates a point where two or more waterways meet, intersect, or branch from one another.
-
E.
transportsWaterTo
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd7743548190a70d3f3c7378aaa7 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.