Triple
T1669269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Joseph River |
E36086
|
entity |
| Predicate | hasWatercourseSystem |
P2432
|
FINISHED |
| Object | St. Joseph River watershed |
—
|
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: St. Joseph River watershed | Statement: [St. Joseph River, hasWatercourseSystem, St. Joseph River watershed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWatercourseSystem Context triple: [St. Joseph River, hasWatercourseSystem, St. Joseph River watershed]
-
A.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
B.
waterwaySystem
chosen
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
-
C.
riverSystem
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
-
D.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abc0e8d5648190915ff689c7ca42bc |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69a907d331748190963d4ab1a2741537 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.