Triple
T34512298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sullivan |
E886055
|
entity |
| Predicate | hasProximityToBodyOfWater |
—
|
GENERATED |
| Object | Oneida Lake |
—
|
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: hasProximityToBodyOfWater Context triple: [Sullivan, hasProximityToBodyOfWater, Oneida Lake]
-
A.
adjacentToBodyOfWater
Indicates that one entity is directly next to or bordering a body of water, such as a lake, river, or ocean.
-
B.
hasNearbyWater
chosen
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
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.
involvesBodyOfWater
Indicates that the relationship or event includes, affects, or takes place in connection with a body of water such as a sea, lake, river, or ocean.
-
E.
locatedInBodyOfWater
Indicates that an entity is situated within or on the surface of a specific 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.