Triple
T25518582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarks Hill Lake |
E639576
|
entity |
| Predicate | isMajorRecreationDestinationFor |
P5644
|
FINISHED |
| Object | Georgia |
—
|
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: Georgia | Statement: [Clarks Hill Lake, isMajorRecreationDestinationFor, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorRecreationDestinationFor Context triple: [Clarks Hill Lake, isMajorRecreationDestinationFor, Georgia]
-
A.
isMajorAttractionFor
chosen
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
-
B.
isMajorAttractionIn
Indicates that something is a primary or highly significant attraction within a particular place or location.
-
C.
areMajorTouristDestinations
Indicates that the referenced places are widely recognized and frequently visited as primary tourist destinations.
-
D.
isResortDestinationFor
Indicates that a place serves as a resort destination specifically intended for or frequented by a particular person, group, or entity.
-
E.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 21, 2026, 2:58 p.m.