Triple
T26510403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afton, Virginia |
E669662
|
entity |
| Predicate | hasNearbyHistoricRoute |
P115769
|
FINISHED |
| Object | Three Notch'd Road (historic) |
—
|
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: Three Notch'd Road (historic) | Statement: [Afton, Virginia, hasNearbyHistoricRoute, Three Notch'd Road (historic)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHistoricRoute Context triple: [Afton, Virginia, hasNearbyHistoricRoute, Three Notch'd Road (historic)]
-
A.
nearHistoricalRoute
chosen
Indicates that one entity is located close to a historically significant route or pathway.
-
B.
hasHistoricalRoute
Indicates that an entity possesses or is associated with a route that has historical significance or origin.
-
C.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic area.
-
D.
historicalRouteVia
Indicates that a historical route or path passed through or was connected by a particular intermediate location or segment.
-
E.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 27, 2026, 1:20 a.m.