Triple

T2345113
Position Surface form Disambiguated ID Type / Status
Subject Brighton E45112 entity
Predicate locatedIn P40 FINISHED
Object East Sussex E25825 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: East Sussex | Statement: [Brighton, locatedIn, East Sussex]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: East Sussex
Context triple: [Brighton, locatedIn, East Sussex]
  • A. East Sussex chosen
    East Sussex is a county in South East England known for its English Channel coastline, the South Downs, and historic towns such as Hastings and Lewes.
  • B. West Sussex
    West Sussex is a county in South East England known for its mix of coastal towns, rural countryside, and historic market settlements.
  • C. Sussex
    Sussex is a traditional British dual-purpose chicken breed valued for both its meat and egg production.
  • D. Swale district
    Swale district is a local government district in Kent, England, encompassing coastal, rural, and urban areas including the Isle of Sheppey and the towns of Sittingbourne and Faversham.
  • E. Essex
    Essex is a county in the east of England, known for its mix of rural landscapes, historic towns, and proximity to London.
  • 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_69a88917935081909b755dbf38e81024 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abc6c7cb9481909405aeb503f804ae completed March 7, 2026, 6:33 a.m.
NED1 Entity disambiguation (via context triple) batch_69b3544c5fcc8190b2d8d61449dfffb3 completed March 13, 2026, 12:03 a.m.
Created at: March 4, 2026, 7:52 p.m.