Triple

T23166546
Position Surface form Disambiguated ID Type / Status
Subject Digby E578724 entity
Predicate hasHarbour P3007 FINISHED
Object Digby Harbour 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: Digby Harbour | Statement: [Digby, hasHarbour, Digby Harbour]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Digby Harbour
Context triple: [Digby, hasHarbour, Digby Harbour]
  • A. Digby Harbour chosen
    Digby Harbour is a coastal port facility in Digby, Nova Scotia, known for supporting local fishing, ferry services, and maritime activities on the Bay of Fundy.
  • B. Dysart Harbour
    Dysart Harbour is a historic small port on the coast of Fife, Scotland, known for its picturesque waterfront and maritime heritage.
  • C. Wick Harbour
    Wick Harbour is a historic fishing and commercial port located in the coastal town of Wick in Caithness, northern Scotland.
  • D. Lark Harbour
    Lark Harbour is a small coastal community in western Newfoundland, Canada, known for its scenic ocean views, nearby mountains, and access to outdoor activities like hiking and fishing.
  • E. Grantley Harbor
    Grantley Harbor is a coastal inlet near Teller on Alaska’s Seward Peninsula, serving as a sheltered harbor along the Bering Sea.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e245fc75348190a0288401044c8af8 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18f2c923c81908b58811fffdcf932 completed April 29, 2026, 4:55 a.m.
Created at: April 17, 2026, 4:03 p.m.