Triple

T11193563
Position Surface form Disambiguated ID Type / Status
Subject Seacombe Ferry Terminal E264863 entity
Predicate locatedIn P40 FINISHED
Object Seacombe E264863 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: Seacombe | Statement: [Seacombe Ferry Terminal, locatedIn, Seacombe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Seacombe
Context triple: [Seacombe Ferry Terminal, locatedIn, Seacombe]
  • A. Seacombe chosen
    Seacombe is a riverside district and ferry terminal on the Wirral Peninsula in England, serving as a key Mersey crossing point to Liverpool.
  • B. Seacombe
    Seacombe is a small coastal bay and cove on the Jurassic Coast in Dorset, England, known for its rugged cliffs and scenic walking paths.
  • C. Combe
    Combe is a small rural village in Oxfordshire, England, known for its traditional English countryside character and proximity to the River Evenlode.
  • D. Sedlescombe
    Sedlescombe is a rural village and civil parish in East Sussex, England, known for its traditional village green and surrounding countryside.
  • E. Cambourne
    Cambourne is a modern, rapidly growing new town in Cambridgeshire, England, developed in the late 20th century and known for its planned residential communities and local amenities.
  • 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_69d6aa9eb9248190b20211772621b4bc completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8be025481909d311b587418dfb2 completed April 9, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69e496ff48448190982d4477039a13d8 completed April 19, 2026, 8:49 a.m.
Created at: April 8, 2026, 9:29 p.m.