Triple

T16786992
Position Surface form Disambiguated ID Type / Status
Subject Mablethorpe and Sutton Urban District E408004 entity
Predicate locatedInHistoricCounty P1069 FINISHED
Object Lindsey E556172 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: Lindsey | Statement: [Mablethorpe and Sutton Urban District, locatedInHistoricCounty, Lindsey]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lindsey
Context triple: [Mablethorpe and Sutton Urban District, locatedInHistoricCounty, Lindsey]
  • A. Lindsey
    Lindsey is a given name commonly used in English-speaking countries for both females and males.
  • B. Lindsey chosen
    Lindsey is a historic region in eastern England, traditionally forming the northern part of the county of Lincolnshire.
  • C. Lindsay
    Lindsay is a small agricultural city in Tulare County, California, known for its citrus production in the San Joaquin Valley.
  • D. Lindsay
    Lindsay is a surname most notably associated with American poet Vachel Lindsay, a key figure in early 20th-century performance and visionary poetry.
  • E. Lindsay
    Lindsay is a feminine given name of English origin, used both as a first name and a surname.
  • 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_69d8839270588190886720d9519bbf8f completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b21b6a408190b0766138cc9a9ee2 completed April 18, 2026, 4:32 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00b28970748190836806c68ad9e230 completed May 10, 2026, 4:30 p.m.
Created at: April 10, 2026, 5:22 a.m.