Triple
T25518566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarks Hill Lake |
E639576
|
entity |
| Predicate | stateBorderForms |
P83394
|
FINISHED |
| Object | portion of the Georgia–South Carolina border |
—
|
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: portion of the Georgia–South Carolina border | Statement: [Clarks Hill Lake, stateBorderForms, portion of the Georgia–South Carolina border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateBorderForms Context triple: [Clarks Hill Lake, stateBorderForms, portion of the Georgia–South Carolina border]
-
A.
borderingStateOrTerritory
Indicates that one state or territory shares a common boundary with another state or territory.
-
B.
borderAgencyUnitedStates
Indicates that the agency operates as or is part of the border control or border security authority of the United States.
-
C.
USStateBorderFor
Indicates that a U.S. state serves as a bordering state for the specified geographic or political entity.
-
D.
stateBorderSectionOf
chosen
Indicates that a specific segment of a boundary line forms part of the overall border of a state.
-
E.
borderStateOf
Indicates that one state shares a common boundary or border with another state.
- 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_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 21, 2026, 2:58 p.m.