Triple
T24044016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanley, Virginia |
E595465
|
entity |
| Predicate | isLocatedInValleySystem |
P56914
|
FINISHED |
| Object | Shenandoah River valley |
—
|
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: Shenandoah River valley | Statement: [Stanley, Virginia, isLocatedInValleySystem, Shenandoah River valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInValleySystem Context triple: [Stanley, Virginia, isLocatedInValleySystem, Shenandoah River valley]
-
A.
valleyLocation
Indicates that one entity is located in, at, or within the geographic bounds of a valley relative to another entity or context.
-
B.
isSideValleyOf
Indicates that one valley is a smaller, secondary valley that branches off from and is connected to a larger main valley.
-
C.
formsValleySystemWith
Indicates that one valley is geographically connected with another to collectively form a larger, integrated valley system.
-
D.
valleyDesignation
Indicates that an entity is formally designated or classified as a valley in relation to a specified geographic or administrative context.
-
E.
isInValley
chosen
Indicates that an entity is located within or occupies the area of a valley.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8dc8f708190ac6257e65c37bde7 |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:10 p.m.