Triple
T8860356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow Spring Run |
E210870
|
entity |
| Predicate | hasWatershedFeature |
P29610
|
FINISHED |
| Object | Appalachian region of West Virginia |
—
|
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: Appalachian region of West Virginia | Statement: [Yellow Spring Run, hasWatershedFeature, Appalachian region of West Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWatershedFeature Context triple: [Yellow Spring Run, hasWatershedFeature, Appalachian region of West Virginia]
-
A.
hasWatershedCharacteristic
chosen
Indicates that a watershed possesses a specified characteristic, feature, or property.
-
B.
hasWatershed
Indicates that one geographic area or feature is part of, drains into, or is hydrologically defined by a particular watershed.
-
C.
hasWatershedWith
Indicates that two geographic areas share or are associated with the same watershed or drainage basin.
-
D.
hasWaterFeatures
Indicates that an entity includes or is associated with water-related elements such as fountains, ponds, streams, or similar features.
-
E.
hasWatershedUse
Indicates that a particular type of use, activity, or function is associated with or applied to a watershed.
- 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e712d08190bfb1c4ba3acaea90 |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.