Triple
T34401674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quay County, New Mexico |
E882993
|
entity |
| Predicate | historicRoutePassesThrough |
P139623
|
FINISHED |
| Object | U.S. Route 66 |
—
|
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: U.S. Route 66 | Statement: [Quay County, New Mexico, historicRoutePassesThrough, U.S. Route 66]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicRoutePassesThrough Context triple: [Quay County, New Mexico, historicRoutePassesThrough, U.S. Route 66]
-
A.
historicRoute
Indicates that a route has historical significance, typically due to its age, past usage, or role in notable events.
-
B.
historicRouteType
Indicates the specific kind or classification of a route in terms of its historical significance or use.
-
C.
historicalRouteVia
chosen
Indicates that a historical route or path passed through or was connected by a particular intermediate location or segment.
-
D.
nearHistoricalRoute
Indicates that one entity is located close to a historically significant route or pathway.
-
E.
travelsThrough
Indicates that something moves along, passes across, or is routed via a particular path, medium, 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0062e6bd788190a7b4f3e5befb5cbb |
completed | May 10, 2026, 10:50 a.m. |
| PD | Predicate disambiguation | batch_6a0061989d188190b4815b2de3e8676f |
completed | May 10, 2026, 10:44 a.m. |
Created at: May 1, 2026, 1:59 a.m.