Triple
T26589788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Wabukayne Park |
E667318
|
entity |
| Predicate | isSurroundingBodyOfWater |
P29911
|
FINISHED |
| Object | Lake Wabukayne |
—
|
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 Wabukayne | Statement: [Lake Wabukayne Park, isSurroundingBodyOfWater, Lake Wabukayne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSurroundingBodyOfWater Context triple: [Lake Wabukayne Park, isSurroundingBodyOfWater, Lake Wabukayne]
-
A.
hasSurroundingWaters
chosen
Indicates that one entity is bordered or encircled by bodies of water associated with another entity.
-
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.
hasSurroundingWatersStatus
Indicates whether and how an entity is characterized in terms of the presence, type, or condition of waters that surround it.
-
D.
locatedInBodyOfWater
Indicates that an entity is situated within or on the surface of a specific body of water.
-
E.
adjacentToBodyOfWater
Indicates that one entity is directly next to or bordering a body of water, such as a lake, river, or ocean.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61524d22881909284d4aa8db7ebdd |
completed | May 2, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 2:07 a.m.