Triple
T34579722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolf Creek Dam |
E887855
|
entity |
| Predicate | createsRecreationArea |
P199712
|
FINISHED |
| Object | Lake Cumberland recreation area |
—
|
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 Cumberland recreation area | Statement: [Wolf Creek Dam, createsRecreationArea, Lake Cumberland recreation area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createsRecreationArea Context triple: [Wolf Creek Dam, createsRecreationArea, Lake Cumberland recreation area]
-
A.
recreationRegion
Indicates that a location or area is designated or used as a region for recreational activities.
-
B.
hasRecreationAreaName
Indicates that a recreation area is associated with a specific name or designation.
-
C.
operatorOfRecreationArea
Indicates that an entity is responsible for managing, running, or overseeing the operations of a recreation area.
-
D.
regenerationArea
Indicates the area or region within which regeneration or renewal of something (such as tissue, habitat, or resources) takes place.
-
E.
isCentralRecreationAreaFor
Indicates that one location serves as the primary or main recreational area for another place or community.
- F. None of above. chosen
Provenance (4 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69ff519a67008190b1eda931fdeff53e |
completed | May 9, 2026, 3:24 p.m. |
Created at: May 1, 2026, 2:03 a.m.