Triple
T37139630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carp Lake Township |
E920068
|
entity |
| Predicate | hasProximityToWaterBodies |
—
|
GENERATED |
| Object | true |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProximityToWaterBodies Context triple: [Carp Lake Township, hasProximityToWaterBodies, true]
-
A.
hasNearbyWater
chosen
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
B.
adjacentToBodyOfWater
Indicates that one entity is directly next to or bordering a body of water, such as a lake, river, or ocean.
-
C.
hasBodyOfWaterType
Indicates that a body of water is classified as being of a particular type or category (such as lake, river, ocean, etc.).
-
D.
hasSurroundingWaters
Indicates that one entity is bordered or encircled by bodies of water associated with another entity.
-
E.
connectsToBodyOfWaterRegion
Indicates that a region has a direct physical connection or boundary with a body of water.
- F. None of above.
Provenance (1 batch)
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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.