Triple

T26562323
Position Surface form Disambiguated ID Type / Status
Subject El Reno E666282 entity
Predicate hasHistoricRoute66Feature P154994 FINISHED
Object vintage motels — 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: vintage motels | Statement: [El Reno, hasHistoricRoute66Feature, vintage motels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricRoute66Feature
Context triple: [El Reno, hasHistoricRoute66Feature, vintage motels]
  • A. isHistoricRoute66Site chosen
    Indicates that a location is situated on, or historically associated with, the original U.S. Route 66 highway and recognized as part of its historic route.
  • B. hasRailroadHistoryWith
    Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
  • C. hasHistoricalRoute
    Indicates that an entity possesses or is associated with a route that has historical significance or origin.
  • D. historicRoute
    Indicates that a route has historical significance, typically due to its age, past usage, or role in notable events.
  • E. hasHistoricStreet
    Indicates that an entity is associated with or located on a street that has recognized historical significance.
  • 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_69ee9cf7e94481909f0d556b36e43572 completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f7805ce6208190ac6dbd9c97989978 completed May 3, 2026, 5:05 p.m.
PD Predicate disambiguation batch_69f77956ec648190ba4fb7e9d83fd107 completed May 3, 2026, 4:35 p.m.
Created at: April 27, 2026, 1:53 a.m.