Triple
T4364260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Dam |
E98733
|
entity |
| Predicate | connectsToReservoir |
P36347
|
FINISHED |
| Object | Lake Barkley via canal |
—
|
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 Barkley via canal | Statement: [Kentucky Dam, connectsToReservoir, Lake Barkley via canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToReservoir Context triple: [Kentucky Dam, connectsToReservoir, Lake Barkley via canal]
-
A.
connectsReservoir
chosen
Indicates that one entity serves as a conduit or linkage that allows water or resources to flow or be transferred between reservoirs.
-
B.
isReservoirOn
Indicates that a reservoir is physically located on or situated atop another specified entity or structure.
-
C.
reservoir
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
-
D.
reservoirType
Indicates the specific kind or classification of a reservoir associated with an entity.
-
E.
reservoirAlsoKnownAs
Indicates that a reservoir is referred to by an alternative name or alias.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e70a748190af6f1b709a0e75e6 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.