Triple

T2028241
Position Surface form Disambiguated ID Type / Status
Subject Heysham E44457 entity
Predicate hasPort P35 FINISHED
Object Heysham Port E44457 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: Heysham Port | Statement: [Heysham, hasPort, Heysham Port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heysham Port
Context triple: [Heysham, hasPort, Heysham Port]
  • A. Heysham chosen
    Heysham is a coastal village and port in Lancashire, England, known for its ferry services across the Irish Sea and its nearby nuclear power stations.
  • B. Mostyn Port
    Mostyn Port is a commercial seaport in North Wales that serves as a key operations and maintenance base for offshore wind farms in the Irish Sea.
  • C. St Mawes
    St Mawes was a former parliamentary borough and small coastal town in Cornwall, England, historically represented in the House of Commons.
  • D. Glasson Dock
    Glasson Dock is a small port village in Lancashire, England, known for its historic dock and marina at the mouth of the River Lune.
  • E. Kinghorn harbour
    Kinghorn harbour is a small coastal harbour in the town of Kinghorn on the Fife coast of Scotland, historically used for local fishing and maritime trade.
  • 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_69a889144f2481909932f0746a93023d completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abb9136f888190b0fd03530e9eda1e completed March 7, 2026, 5:35 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae304cc62c81909d152ee6ae543d7e completed March 9, 2026, 2:28 a.m.
Created at: March 4, 2026, 7:38 p.m.