Triple
T37132541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mill Springs |
E919561
|
entity |
| Predicate | frontlineRiver |
P2502
|
FINISHED |
| Object | Cumberland River |
—
|
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: Cumberland River | Statement: [Battle of Mill Springs, frontlineRiver, Cumberland River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontlineRiver Context triple: [Battle of Mill Springs, frontlineRiver, Cumberland River]
-
A.
facedRiver
Indicates that an entity is oriented toward or directly facing a river.
-
B.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
C.
frontLine
chosen
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
-
D.
upstreamRiver
Indicates that one river is located or flows in an upstream direction relative to another river within the same watercourse system.
-
E.
runOfTheRiver
Indicates a relationship where a hydroelectric facility operates using the natural flow and elevation drop of a river without significant water storage or regulation by a large 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.