Triple

T29154536
Position Surface form Disambiguated ID Type / Status
Subject Keystone–Port Townsend route E739000 entity
Predicate terminusOnWhidbeyIsland P170747 FINISHED
Object Keystone, Washington 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: Keystone, Washington | Statement: [Keystone–Port Townsend route, terminusOnWhidbeyIsland, Keystone, Washington]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: terminusOnWhidbeyIsland
Context triple: [Keystone–Port Townsend route, terminusOnWhidbeyIsland, Keystone, Washington]
  • A. terminusOnVancouverIsland
    Indicates that the endpoint or terminus of something (such as a route, line, or service) is located on Vancouver Island.
  • B. terminusInland
    Indicates that something ends, concludes, or has its final point within an inland area rather than at a coast or shoreline.
  • C. terminusCoastal
    Indicates that the endpoint or terminus of something (e.g., a route, line, or feature) is located on or directly adjacent to a coast.
  • D. hasIslandTerminus chosen
    Indicates that something (such as a route, line, or connection) ends or terminates on an island.
  • E. terminusWestConnection
    Indicates that one entity serves as the western endpoint where it connects to another entity or route.
  • 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_69f07cb46f148190874eb8576a447567 completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69f6a28c7c148190bfc980aad9f678ca completed May 3, 2026, 1:19 a.m.
PD Predicate disambiguation batch_69f69fe1e3c88190830bb2e9f407357e completed May 3, 2026, 1:07 a.m.
Created at: April 28, 2026, 11:44 a.m.