Triple

T27117
Position Surface form Disambiguated ID Type / Status
Subject U.S. Route 1 E543 entity
Predicate terminusCity P1866 FINISHED
Object Fort Kent E6034 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: Fort Kent | Statement: [U.S. Route 1, terminusCity, Fort Kent]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fort Kent
Context triple: [U.S. Route 1, terminusCity, Fort Kent]
  • A. Fort Kent, Maine chosen
    Fort Kent, Maine is a small town in northern Aroostook County known for its location at the Canadian border and as a gateway to the North Maine Woods.
  • B. Weston
    Weston is a suburban town in eastern Massachusetts known for its residential character, conservation land, and commuter access to Boston.
  • C. Kanesville
    Kanesville was the mid-19th-century Mormon settlement that later became the city of Council Bluffs, Iowa.
  • D. Newton Highlands
    Newton Highlands is a village and residential neighborhood within the city of Newton, Massachusetts, known for its historic district and Green Line D-branch service.
  • E. Valley Wells
    Valley Wells is a small locality situated within California’s Mojave Desert, known primarily as a remote desert community along major regional travel routes.
  • 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_69a243b4ac2c8190b93c303df797b7b2 completed Feb. 28, 2026, 1:24 a.m.
NER Named-entity recognition batch_69a2481f9eac819093d9a950eb1ab109 completed Feb. 28, 2026, 1:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69a266e34b548190a0fc4dea2cf37e52 completed Feb. 28, 2026, 3:54 a.m.
Created at: Feb. 28, 2026, 1:34 a.m.