Triple
T33241989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Cumberland |
E850985
|
entity |
| Predicate | hasStateResortParkOnShore |
P192710
|
FINISHED |
| Object | Lake Cumberland State Resort Park |
—
|
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 State Resort Park | Statement: [Lake Cumberland, hasStateResortParkOnShore, Lake Cumberland State Resort Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStateResortParkOnShore Context triple: [Lake Cumberland, hasStateResortParkOnShore, Lake Cumberland State Resort Park]
-
A.
stateParkAtShore
chosen
Indicates that a state park is located along or directly adjacent to a shoreline.
-
B.
hasCoastlineResort
Indicates that a geographic area or location contains a resort situated along its coastline.
-
C.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
D.
hasMarinePark
Indicates that an entity possesses, contains, or is associated with a designated marine park area.
-
E.
hasBeachResortStatus
Indicates that an entity holds the designation or classification of being a beach resort.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: May 1, 2026, 1:31 a.m.