Triple
T10256957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harwood, Missouri |
E240495
|
entity |
| Predicate | roadAccessRegion |
P22549
|
FINISHED |
| Object | Vernon County road network |
—
|
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: Vernon County road network | Statement: [Harwood, Missouri, roadAccessRegion, Vernon County road network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadAccessRegion Context triple: [Harwood, Missouri, roadAccessRegion, Vernon County road network]
-
A.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
B.
roadAccessFrom
chosen
Indicates that one location can be reached from another via a usable road connection.
-
C.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
D.
roadCorridorIncludes
Indicates that a specified road corridor spatially contains or encompasses another element or segment within its defined bounds.
-
E.
roadAccessSeason
Indicates the time of year or season during which road access to a place or area is available or permitted.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2b5853081909cd0397e08a0f44d |
completed | April 7, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69d4d1edae6881909a65201b8e51ea0a |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:31 a.m.