Triple
T26363605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NV 265 |
E660271
|
entity |
| Predicate | connectsTownToHighway |
P12245
|
FINISHED |
| Object | Goldfield to U.S. Route 95 |
—
|
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: Goldfield to U.S. Route 95 | Statement: [NV 265, connectsTownToHighway, Goldfield to U.S. Route 95]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsTownToHighway Context triple: [NV 265, connectsTownToHighway, Goldfield to U.S. Route 95]
-
A.
connectsToHighway
chosen
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
B.
motorwayConnectionWith
Indicates that two locations are directly connected by a motorway, allowing vehicular travel between them via that road.
-
C.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
-
D.
connectsRoadNetwork
Indicates that one entity is linked to another as part of the same road network, enabling continuous vehicular or transport connectivity between them.
-
E.
expresswayServedBy
Indicates that a particular expressway is provided with service or access by a specified facility, route, or service entity.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 26, 2026, 10:53 p.m.