Triple
T7798324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strouds Run State Park |
E180356
|
entity |
| Predicate | waterBodyUse |
P44236
|
FINISHED |
| Object | no-wake boating on Dow Lake |
—
|
LITERAL FINISHED |
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: no-wake boating on Dow Lake | Statement: [Strouds Run State Park, waterBodyUse, no-wake boating on Dow Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterBodyUse Context triple: [Strouds Run State Park, waterBodyUse, no-wake boating on Dow Lake]
-
A.
waterbodyUsedFor
chosen
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
-
B.
waterQualityUse
Indicates the way in which water quality is evaluated, classified, or applied for specific purposes or uses.
-
C.
appliesToWaterBody
Indicates that something (such as a rule, condition, property, or effect) is relevant or applicable specifically to a particular water body.
-
D.
reservoirUse
Indicates the way a reservoir is utilized or the purpose for which its stored water is used.
-
E.
hasWaterfrontUse
Indicates that an entity is used, designated, or suitable for activities or purposes directly related to a waterfront or shoreline area.
- 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_69ca827d22208190b4dc5aa680edcf5d |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:32 p.m.