Triple

T4269341
Position Surface form Disambiguated ID Type / Status
Subject White Pass E96901 entity
Predicate near P350 FINISHED
Object Skagway E17513 NE 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: Skagway | Statement: [White Pass, near, Skagway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Skagway
Context triple: [White Pass, near, Skagway]
  • A. Skagway chosen
    Skagway is a historic Alaskan town known as a gateway to the Klondike Gold Rush region and a popular cruise ship stop in the Inside Passage.
  • B. Ketchikan
    Ketchikan is a coastal city in southeastern Alaska known for its rich Native Alaskan culture, historic downtown, and status as a major cruise ship and fishing port.
  • C. Petersburg, Alaska
    Petersburg, Alaska is a small fishing town in Southeast Alaska known for its strong Norwegian heritage and thriving commercial fishing industry.
  • D. Dyea, Alaska
    Dyea, Alaska is a historic ghost town and former boomtown near Skagway that served as a major gateway to the Klondike Gold Rush via the Chilkoot Trail.
  • E. Yakutat
    Yakutat is a small coastal city in southeastern Alaska known for its remote location, fishing industry, and access to the Gulf of Alaska’s rugged natural landscapes.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69b34543f06c8190915ebb1a4574ffa9 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34ffa30c08190913622ffec47d33d completed March 12, 2026, 11:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69bfc0140a548190a9fb54c267622fb1 completed March 22, 2026, 10:10 a.m.
Created at: March 12, 2026, 11:07 p.m.