Triple
T5150009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley of Death |
E116169
|
entity |
| Predicate | crossedBy |
P416
|
FINISHED |
| Object | Plum Run |
E128304
|
NE 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: Plum Run | Statement: [Valley of Death, crossedBy, Plum Run]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Plum Run Context triple: [Valley of Death, crossedBy, Plum Run]
-
A.
Plum Run
chosen
Plum Run is a small stream on the Gettysburg Battlefield in Pennsylvania, historically significant for flowing through key areas of the 1863 Civil War fighting.
-
B.
Kingham Run
Kingham Run is a local running event associated with the village of Kingham, typically attracting community participants for an organized road or cross-country race.
-
C.
Edwards Run
Edwards Run is a small stream in West Virginia that serves as a tributary within the Cacapon River watershed.
-
D.
Shanondale Springs Run
Shanondale Springs Run is a small stream in West Virginia that feeds into the Cacapon River and flows near the historic Shanondale Springs resort area.
-
E.
Sulphur Spring Run
Sulphur Spring Run is a small stream in the Opequon Creek watershed that contributes to the larger drainage system in the region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd4446c0e08190a7c29dc74976bf03 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd78b2a1748190b896ba0f53927118 |
completed | March 20, 2026, 4:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69beefa840288190ad0e1ab7af8b9c4c |
completed | March 21, 2026, 7:21 p.m. |
Created at: March 20, 2026, 1:43 p.m.