Triple

T21467950
Position Surface form Disambiguated ID Type / Status
Subject Tyne estuary E529641 entity
Predicate adjacentTown P3883 FINISHED
Object Tynemouth 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: Tynemouth | Statement: [Tyne estuary, adjacentTown, Tynemouth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tynemouth
Context triple: [Tyne estuary, adjacentTown, Tynemouth]
  • A. Tynemouth chosen
    Tynemouth is a coastal town in Tyne and Wear, England, known for its historic priory and castle overlooking long sandy beaches at the mouth of the River Tyne.
  • B. Hartlepool
    Hartlepool is a coastal town in County Durham, England, known historically for its shipbuilding and maritime heritage.
  • C. Maryport
    Maryport is a coastal town in Cumbria, England, known for its historic harbor, Roman heritage, and maritime history.
  • D. North Shields
    North Shields is a coastal town on the north bank of the River Tyne in North East England, historically known for its fishing and shipbuilding industries.
  • E. South Shields
    South Shields is a coastal town in Tyne and Wear, England, known historically for its shipbuilding and as part of the Tyneside urban area.
  • 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_69e0c459acb481909bb6ee452a0045c7 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9e9f415d48190a2b0993a4f3c018f completed April 23, 2026, 9:44 a.m.
Created at: April 16, 2026, 6:15 p.m.