Triple
T30144054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beckham County, Oklahoma |
E766203
|
entity |
| Predicate | hasHistoricHighway |
P17497
|
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: [Beckham County, Oklahoma, hasHistoricHighway, U.S. Route 66]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricHighway Context triple: [Beckham County, Oklahoma, hasHistoricHighway, U.S. Route 66]
-
A.
hasRoadHistory
Indicates that there exists a recorded history or sequence of past states, events, or changes associated with a particular road.
-
B.
hasHistoricStreet
chosen
Indicates that an entity is associated with or located on a street that has recognized historical significance.
-
C.
formerConstituentHighway
Indicates that a highway was once part of, but is no longer included in, another highway or highway system.
-
D.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
-
E.
containsStateHighway
Indicates that a geographic area or region includes within its boundaries at least one designated state highway.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: April 29, 2026, 7:18 p.m.