Triple
T36478821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walnut Grove, Virginia |
E898749
|
entity |
| Predicate | roadAccessIn |
P22549
|
FINISHED |
| Object | Washington County, Virginia |
—
|
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: Washington County, Virginia | Statement: [Walnut Grove, Virginia, roadAccessIn, Washington County, Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadAccessIn Context triple: [Walnut Grove, Virginia, roadAccessIn, Washington County, Virginia]
-
A.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
B.
roadAccessArea
Indicates that an area is designated for or provides access to a road, such as for entry, exit, or connection.
-
C.
roadAccessFrom
chosen
Indicates that one location can be reached from another via a usable road connection.
-
D.
roadAccessDetail
Indicates details about how a location is accessed by road, such as the type, quality, or characteristics of the connecting roadway.
-
E.
roadAccessOftenAffectedBy
Indicates that the normal ability to use or travel on a road is frequently disrupted or limited by the specified factor or condition.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.