Triple
T33883962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coosa River reservoir system |
E868572
|
entity |
| Predicate | stateBorderContext |
P196640
|
FINISHED |
| Object | Alabama–Georgia region |
—
|
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: Alabama–Georgia region | Statement: [Coosa River reservoir system, stateBorderContext, Alabama–Georgia region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateBorderContext Context triple: [Coosa River reservoir system, stateBorderContext, Alabama–Georgia region]
-
A.
stateBorderSectionOf
Indicates that a specific segment of a boundary line forms part of the overall border of a state.
-
B.
borderStateOf
Indicates that one state shares a common boundary or border with another state.
-
C.
provinceBordering
Indicates that two provinces share a common boundary or border with each other.
-
D.
borderingStateOrProvince
Indicates that one state or province shares a common boundary with another state or province.
-
E.
borderingStateOrTerritory
Indicates that one state or territory shares a common boundary with another state or territory.
- F. None of above. chosen
Provenance (4 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
| PDg | Predicate description generation | batch_69fe5ec84910819094cb15269ace7c51 |
completed | May 8, 2026, 10:08 p.m. |
Created at: May 1, 2026, 1:48 a.m.