Triple
T3735391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississagi River |
E79169
|
entity |
| Predicate | isInWatershed |
P17416
|
FINISHED |
| Object | Lake Huron 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: Lake Huron watershed | Statement: [Mississagi River, isInWatershed, Lake Huron watershed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInWatershed Context triple: [Mississagi River, isInWatershed, Lake Huron watershed]
-
A.
hasWatershed
chosen
Indicates that one geographic area or feature is part of, drains into, or is hydrologically defined by a particular watershed.
-
B.
hasWatershedCharacteristic
Indicates that a watershed possesses a specified characteristic, feature, or property.
-
C.
watershedBetween
Indicates that a geographic feature or boundary serves as the dividing line between two drainage basins or river systems.
-
D.
isInLand
Indicates that one entity is located within the geographical boundaries of a land area or territory of another entity.
-
E.
watershedType
Indicates the classification or category of a watershed associated with an entity (e.g., by hydrologic, ecological, or management type).
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb3b399c819091b42209925c0d8f |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.