Triple
T26852598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moore Haven, Florida |
E676098
|
entity |
| Predicate | majorWaterBodyNearby |
P47449
|
FINISHED |
| Object | Lake Okeechobee |
—
|
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 Okeechobee | Statement: [Moore Haven, Florida, majorWaterBodyNearby, Lake Okeechobee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorWaterBodyNearby Context triple: [Moore Haven, Florida, majorWaterBodyNearby, Lake Okeechobee]
-
A.
nearestLargeBodyOfWater
chosen
Indicates the closest significant body of water in proximity to a given location or entity.
-
B.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
C.
connectedBodyOfWater
Indicates that two geographic locations are linked by a continuous body of water through which water can flow between them.
-
D.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
E.
waterBodyCreatedNearby
Indicates that a water body has been formed or established in close spatial proximity to a specified reference location or 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 27, 2026, 5:18 a.m.