Triple
T29769992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polk City |
E755218
|
entity |
| Predicate | hasWaterRecreationAccess |
P8966
|
FINISHED |
| Object | Saylorville Lake |
—
|
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: Saylorville Lake | Statement: [Polk City, hasWaterRecreationAccess, Saylorville Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterRecreationAccess Context triple: [Polk City, hasWaterRecreationAccess, Saylorville Lake]
-
A.
hasFishingAccess
Indicates that an entity is permitted or able to fish in or otherwise use a particular water body or fishing area.
-
B.
hasWaterfrontAccessTo
Indicates that one entity is directly adjacent to and can physically access a particular body of water, such as a lake, river, or ocean.
-
C.
recreationAccess
chosen
Indicates that one entity provides or has the ability to use recreational facilities, activities, or spaces associated with another entity.
-
D.
hasWaterfrontUse
Indicates that an entity is used, designated, or suitable for activities or purposes directly related to a waterfront or shoreline area.
-
E.
hasCoastalRecreation
Indicates that an entity provides, supports, or is associated with recreational activities occurring along a coast or shoreline.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 8:41 p.m.