Triple

T10538878
Position Surface form Disambiguated ID Type / Status
Subject Hornby Dock E248642 entity
Predicate connectedTo P37 FINISHED
Object Alexandra Dock E223806 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: Alexandra Dock | Statement: [Hornby Dock, connectedTo, Alexandra Dock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alexandra Dock
Context triple: [Hornby Dock, connectedTo, Alexandra Dock]
  • A. Alexandra Dock
    Alexandra Dock is a major commercial dock in Kingston upon Hull, England, historically important for handling cargo and supporting the city's maritime trade.
  • B. Alexandra Dock chosen
    Alexandra Dock is a major dock facility within the Port of Liverpool, historically important for handling cargo and supporting the city’s maritime trade.
  • C. King George Dock
    King George Dock is a major commercial port facility in Kingston upon Hull, England, handling cargo and passenger traffic on the Humber Estuary.
  • D. Victoria Dock
    Victoria Dock is a waterfront harbor area in Hobart, Tasmania, known for its fishing fleet, seafood restaurants, and proximity to the city’s historic docks.
  • E. Victoria Dock
    Victoria Dock is a harbour facility in Hartlepool, England, forming part of the town’s historic port and maritime infrastructure.
  • 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_69d381c5c7448190bec34bee7ec72bac completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d50a5730d88190b266a940faf53f65 completed April 7, 2026, 1:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69d90e5b827881909e87651a88976f18 completed April 10, 2026, 2:51 p.m.
Created at: April 6, 2026, 12:31 p.m.