Triple
T29037042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holland River watershed |
E737888
|
entity |
| Predicate | waterFlowsDirection |
P8846
|
FINISHED |
| Object | generally northward toward Lake Simcoe |
—
|
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: generally northward toward Lake Simcoe | Statement: [Holland River watershed, waterFlowsDirection, generally northward toward Lake Simcoe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterFlowsDirection Context triple: [Holland River watershed, waterFlowsDirection, generally northward toward Lake Simcoe]
-
A.
waterwayDirection
Indicates the directional flow or orientation of a waterway relative to a reference point or path.
-
B.
drainageDirection
chosen
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
-
C.
waterFlowsThrough
Indicates that water moves along a path or channel passing from one location or object to another.
-
D.
pilgrimFlowDirection
Indicates the direction in which pilgrims move or travel along a route, path, or within a pilgrimage site.
-
E.
feedsWatersThatReach
Indicates that one body of water supplies or contributes flow to other waters that it eventually reaches.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 28, 2026, 9:59 a.m.