Triple

T16000447
Position Surface form Disambiguated ID Type / Status
Subject Shields Ferry E388076 entity
Predicate serves P98 FINISHED
Object South Shields E116755 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: South Shields | Statement: [Shields Ferry, serves, South Shields]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: South Shields
Context triple: [Shields Ferry, serves, South Shields]
  • A. South Shields chosen
    South Shields is a coastal town in Tyne and Wear, England, known historically for its shipbuilding and as part of the Tyneside urban area.
  • B. 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.
  • C. Tynemouth
    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.
  • D. Redcar
    Redcar is a seaside town and resort on the North Sea coast in North Yorkshire, England, known for its beaches and historic links to the steel industry.
  • E. Hartlepool
    Hartlepool is a coastal town in County Durham, England, known historically for its shipbuilding and maritime heritage.
  • 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_69d86daa562c81908aacc179c0fe8fb5 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e157fba9748190ac8fc27b167d49f7 completed April 16, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffe470cd5881909cc0c48b3a540d61 completed May 10, 2026, 1:50 a.m.
Created at: April 10, 2026, 4:55 a.m.