Triple

T19425602
Position Surface form Disambiguated ID Type / Status
Subject Puerto Vallarta–San Francisco–Seattle E485971 entity
Predicate hasSegment P3574 FINISHED
Object San Francisco–Seattle NE NERFINISHED

How this triple was built (3 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: San Francisco–Seattle | Statement: [Puerto Vallarta–San Francisco–Seattle, hasSegment, San Francisco–Seattle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: San Francisco–Seattle
Context triple: [Puerto Vallarta–San Francisco–Seattle, hasSegment, San Francisco–Seattle]
  • A. Eugene–Portland–Seattle–Vancouver corridor
    The Eugene–Portland–Seattle–Vancouver corridor is a major north–south passenger rail and transportation route in the Pacific Northwest, linking key cities in Oregon, Washington, and British Columbia.
  • B. Vancouver–Seattle corridor
    The Vancouver–Seattle corridor is a major bi-national urban and transportation axis linking metropolitan regions in southwestern British Columbia and northwestern Washington State.
  • C. Los Angeles–San Francisco
    Los Angeles–San Francisco refers to the major intercity corridor in California connecting the state’s largest southern metropolis with its iconic northern bay city, historically served by prominent rail and highway routes.
  • D. Seattle–Tacoma urban corridor
    The Seattle–Tacoma urban corridor is a densely developed metropolitan region in western Washington State that encompasses and connects the major cities of Seattle and Tacoma along the Puget Sound.
  • E. Puerto Vallarta–San Francisco–Seattle
    Puerto Vallarta–San Francisco–Seattle is the scheduled international and domestic route along the U.S. West Coast and Mexico’s Pacific coast that was served by Alaska Airlines Flight 261.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: San Francisco–Seattle
Target entity description: San Francisco–Seattle is a major air route connecting the San Francisco Bay Area with the Seattle metropolitan region in the Pacific Northwest.
  • A. Eugene–Portland–Seattle–Vancouver corridor
    The Eugene–Portland–Seattle–Vancouver corridor is a major north–south passenger rail and transportation route in the Pacific Northwest, linking key cities in Oregon, Washington, and British Columbia.
  • B. Vancouver–Seattle corridor
    The Vancouver–Seattle corridor is a major bi-national urban and transportation axis linking metropolitan regions in southwestern British Columbia and northwestern Washington State.
  • C. Los Angeles–San Francisco
    Los Angeles–San Francisco refers to the major intercity corridor in California connecting the state’s largest southern metropolis with its iconic northern bay city, historically served by prominent rail and highway routes.
  • D. Seattle–Tacoma urban corridor
    The Seattle–Tacoma urban corridor is a densely developed metropolitan region in western Washington State that encompasses and connects the major cities of Seattle and Tacoma along the Puget Sound.
  • E. Puerto Vallarta–San Francisco–Seattle
    Puerto Vallarta–San Francisco–Seattle is the scheduled international and domestic route along the U.S. West Coast and Mexico’s Pacific coast that was served by Alaska Airlines Flight 261.
  • F. None of above. chosen

Provenance (2 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_69d8e8d688f881909c85104a62e09d8a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63218772c8190a48b6cb01bd12b73 completed April 20, 2026, 2:03 p.m.
Created at: April 10, 2026, 1:37 p.m.