Triple

T8619243
Position Surface form Disambiguated ID Type / Status
Subject Millbay Docks E204120 entity
Predicate adjacentTo P224 FINISHED
Object Millbay E746785 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 | Statement: [Millbay Docks, adjacentTo, Millbay]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Millbay
Context triple: [Millbay Docks, adjacentTo, Millbay]
  • A. Millbay chosen
    Millbay is a tidal harbor and waterfront area in Plymouth, Devon, England, known for its docks, ferry services, and maritime heritage.
  • B. Wereham
    Wereham is a small rural village in Norfolk, England, known for its historic church and traditional village green.
  • C. Stone Harbor
    Stone Harbor is a small, upscale seaside resort town on the southern New Jersey coast known for its beaches, bird sanctuary, and family-oriented vacation atmosphere.
  • D. Sandhaven
    Sandhaven is a small coastal village in the Buchan area of Aberdeenshire, northeast Scotland, historically associated with fishing and maritime activity.
  • E. Fairhaven
    Fairhaven is a historic coastal town in southeastern Massachusetts known for its picturesque harbor, rich maritime heritage, and well-preserved 19th-century architecture.
  • 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_69ca832ceab8819096e4a9f546695079 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cc471458f48190a6d8858f8074727d completed March 31, 2026, 10:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69cecc92beb48190ad406f48e58d9d0c completed April 2, 2026, 8:07 p.m.
Created at: March 30, 2026, 6:26 p.m.