Triple
T18391606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hales Bar Dam |
E449741
|
entity |
| Predicate | reservoirLaterKnownAs |
P42412
|
FINISHED |
| Object | Nickajack Lake |
—
|
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: Nickajack Lake | Statement: [Hales Bar Dam, reservoirLaterKnownAs, Nickajack Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservoirLaterKnownAs Context triple: [Hales Bar Dam, reservoirLaterKnownAs, Nickajack Lake]
-
A.
reservoirAlsoKnownAs
chosen
Indicates that a reservoir is referred to by an alternative name or alias.
-
B.
reservoir
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
-
C.
reservoirNameEtymology
Indicates the origin or source of a reservoir’s name, such as the historical, cultural, or linguistic reason it was given that name.
-
D.
reservoirLocation
Indicates that a reservoir is geographically located at or within a specified place or region.
-
E.
namedReservoirSurfaceName
Indicates that a specific name is assigned to the surface of a reservoir.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e518422e488190bd06fad72efa1641 |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.