Triple

T14736930
Position Surface form Disambiguated ID Type / Status
Subject Plymouth Harbour E346235 entity
Predicate hasNearbyPort P942 FINISHED
Object Millbay Docks E204120 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: Millbay Docks | Statement: [Plymouth Harbour, hasNearbyPort, Millbay Docks]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Millbay Docks
Context triple: [Plymouth Harbour, hasNearbyPort, Millbay Docks]
  • A. Millbay Docks chosen
    Millbay Docks is a historic commercial and ferry port area in Plymouth, England, known for its maritime trade and cross-channel services.
  • B. Kurast Docks
    Kurast Docks is a coastal hub and primary waypoint area in Diablo II, serving as the player’s base of operations in Act III.
  • C. Stalbridge Dock
    Stalbridge Dock is a component basin within the Garston Docks complex in Liverpool, historically used for handling maritime cargo and shipping.
  • D. Dungeness Dock
    Dungeness Dock is a waterfront landing area associated with the historic Dungeness estate on Cumberland Island, Georgia, serving as a primary access point by boat.
  • E. Colman Dock
    Colman Dock is a major ferry terminal on Seattle’s downtown waterfront that serves as a key hub for Washington State Ferries across Puget Sound.
  • 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_69d822e6f1c88190bc494d491a907114 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec73114cc819088e1101b689fc70b completed April 14, 2026, 11:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdfb90378481909a3083680f11101c completed May 8, 2026, 3:04 p.m.
Created at: April 10, 2026, 1:29 a.m.