Triple
T27720513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lac Vieux Desert |
E698939
|
entity |
| Predicate | watercourseOriginatesHere |
P25636
|
FINISHED |
| Object | Wisconsin River |
—
|
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: Wisconsin River | Statement: [Lac Vieux Desert, watercourseOriginatesHere, Wisconsin River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseOriginatesHere Context triple: [Lac Vieux Desert, watercourseOriginatesHere, Wisconsin River]
-
A.
sourceOfWatercourse
chosen
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
-
B.
watercourseFor
Indicates that one entity serves as the watercourse (such as a river or channel) associated with, carrying, or draining another entity.
-
C.
majorRiverSource
Indicates that one entity is the primary originating source or headwaters location of a major river.
-
D.
isWatercourseOf
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.
watercourseHelpsForm
Indicates that a watercourse contributes to the creation, shaping, or delineation of another geographic feature or boundary.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 3:06 p.m.