Triple
T28238326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watervliet, Michigan |
E711943
|
entity |
| Predicate | nearbyWaterBodyType |
P49291
|
FINISHED |
| Object | inland lakes |
—
|
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: inland lakes | Statement: [Watervliet, Michigan, nearbyWaterBodyType, inland lakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyWaterBodyType Context triple: [Watervliet, Michigan, nearbyWaterBodyType, inland lakes]
-
A.
lakeTypeNearby
Indicates that one entity is located near another entity that is classified as a particular type of lake.
-
B.
hasBodyOfWaterType
Indicates that a body of water is classified as being of a particular type or category (such as lake, river, ocean, etc.).
-
C.
nearestLargeBodyOfWater
Indicates the closest significant body of water in proximity to a given location or entity.
-
D.
waterbodyType
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
E.
hasNearbyWater
chosen
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
- 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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 27, 2026, 10:56 p.m.