Triple

T1203054
Position Surface form Disambiguated ID Type / Status
Subject East Sussex E25825 entity
Predicate contains P35 FINISHED
Object Newhaven E126840 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: Newhaven | Statement: [East Sussex, contains, Newhaven]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Newhaven
Context triple: [East Sussex, contains, Newhaven]
  • A. Newhaven
    Newhaven is a historic coastal district of Edinburgh, Scotland, known for its former fishing village, harbor, and maritime heritage.
  • B. Newhaven, England chosen
    Newhaven, England is a coastal town and ferry port in East Sussex, known historically as a Channel crossing point and for giving its name to New Haven, Connecticut.
  • C. Dover
    Dover is a small town in eastern Dutchess County, New York, known for its rural character and location near the Connecticut border.
  • D. Dover
    Dover is a coastal town in southeast England best known for its white chalk cliffs and its strategic port facing the narrowest part of the English Channel.
  • E. Dover
    Dover is one of the oldest permanent European settlements in what is now the U.S. state of New Hampshire, historically significant as an early colonial town and port.
  • 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_69a4942b30f08190a91c60573e16b5ef completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bdbda0b081909c0147121a945e27 completed March 1, 2026, 10:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69acd46eefa48190baebc12fdf916941 completed March 8, 2026, 1:44 a.m.
Created at: March 1, 2026, 7:46 p.m.