Triple
T29640977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapin, South Carolina |
E755858
|
entity |
| Predicate | recreationalFeature |
P162806
|
FINISHED |
| Object | access to boating on Lake Murray |
—
|
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: access to boating on Lake Murray | Statement: [Chapin, South Carolina, recreationalFeature, access to boating on Lake Murray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationalFeature Context triple: [Chapin, South Carolina, recreationalFeature, access to boating on Lake Murray]
-
A.
recreationLocation
Indicates the place where a recreational activity or leisure pursuit occurs.
-
B.
hasRecreationalAspect
Indicates that something includes, involves, or is characterized by a recreational or leisure-related component or purpose.
-
C.
recreationActivitiesSupported
chosen
Indicates that an entity provides, allows, or is compatible with certain recreational activities.
-
D.
recreationAccessPoint
Indicates a location or facility that serves as an entry or starting point for engaging in recreational activities.
-
E.
isRecreationalArea
Indicates that a place or space is designated and used primarily for leisure, relaxation, or recreational activities.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f66ecece888190a653f1b981493834 |
completed | May 2, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:46 p.m.