Triple

T15733106
Position Surface form Disambiguated ID Type / Status
Subject Metlakatla E381393 entity
Predicate locatedNearCity P3883 FINISHED
Object Ketchikan E15456 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: Ketchikan | Statement: [Metlakatla, locatedNearCity, Ketchikan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ketchikan
Context triple: [Metlakatla, locatedNearCity, Ketchikan]
  • A. Ketchikan chosen
    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.
  • B. Skagway
    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.
  • C. Anchorage
    Anchorage is a major Alaskan city known as a key economic, transportation, and cultural hub for the state and the broader Arctic region.
  • D. Petersburg, Alaska
    Petersburg, Alaska is a small fishing town in Southeast Alaska known for its strong Norwegian heritage and thriving commercial fishing industry.
  • E. Sitka
    Sitka is a historic coastal city in southeastern Alaska known for its Tlingit and Russian heritage, scenic island setting, and abundant wildlife.
  • 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_69d86d9cdb648190bf3171be0bd7d872 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e04fd3614481908b2694b1d3550058 completed April 16, 2026, 2:56 a.m.
NED1 Entity disambiguation (via context triple) batch_6a002d966ffc8190aa0d9d3abf8ad593 completed May 10, 2026, 7:02 a.m.
Created at: April 10, 2026, 4:46 a.m.