Triple
T15720375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buford Dam |
E381076
|
entity |
| Predicate | downstreamAffects |
P25489
|
FINISHED |
| Object | Lake Lanier outflows |
—
|
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: Lake Lanier outflows | Statement: [Buford Dam, downstreamAffects, Lake Lanier outflows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: downstreamAffects Context triple: [Buford Dam, downstreamAffects, Lake Lanier outflows]
-
A.
hasUpstreamImpactOn
Indicates that one entity’s actions, changes, or outputs affect another entity that is positioned earlier in a process, flow, or dependency chain.
-
B.
downstreamFrom
Indicates that one entity is located or occurs at a point further along the natural flow or direction of another entity, typically in a linear or directional system such as a river, pipeline, or process sequence.
-
C.
hasDownstreamConfluence
Indicates that one watercourse or flow feature joins or merges into another at a point located further downstream.
-
D.
areAffectedBy
chosen
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
E.
downstreamUse
Indicates that one entity makes use of the outputs, results, or products generated by another entity at a later stage in a process or workflow.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb0b51081908e652ec4992296fa |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.