Triple
T9695316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Hartwell |
E234633
|
entity |
| Predicate | recreationalArea |
P5383
|
FINISHED |
| Object | Corps of Engineers campgrounds |
—
|
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: Corps of Engineers campgrounds | Statement: [Lake Hartwell, recreationalArea, Corps of Engineers campgrounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationalArea Context triple: [Lake Hartwell, recreationalArea, Corps of Engineers campgrounds]
-
A.
isRecreationalArea
Indicates that a place or space is designated and used primarily for leisure, relaxation, or recreational activities.
-
B.
hasRecreationalArea
chosen
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
C.
operatorOfRecreationArea
Indicates that an entity is responsible for managing, running, or overseeing the operations of a recreation area.
-
D.
withinRecreationArea
Indicates that one entity is located inside the spatial bounds of a designated recreation area associated with another entity.
-
E.
parkArea
Indicates that an area of land is designated and used as a park or recreational green space.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d366c488190bc153c68fef197c2 |
completed | April 1, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b9e93c8190947cce56a3925364 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.