Triple
T35821430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand River valley |
E1035511
|
entity |
| Predicate | mouthWaterBody |
P43761
|
FINISHED |
| Object | Lake Michigan |
—
|
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: Lake Michigan | Statement: [Grand River valley, mouthWaterBody, Lake Michigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mouthWaterBody Context triple: [Grand River valley, mouthWaterBody, Lake Michigan]
-
A.
hasMouthWaterbody
chosen
Indicates that a waterbody has a mouth, i.e., the location or feature where it empties or flows into another waterbody or area.
-
B.
mouthOfWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water or another watercourse.
-
C.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
-
D.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
E.
addressesWaterBody
Indicates that an action, plan, or measure is directed toward managing, affecting, or dealing with a specific water body.
- 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.