Triple

T22589719
Position Surface form Disambiguated ID Type / Status
Subject Hartington Hall E564909 entity
Predicate locatedIn P40 FINISHED
Object Hartington NE NERFINISHED

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: Hartington | Statement: [Hartington Hall, locatedIn, Hartington]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hartington
Context triple: [Hartington Hall, locatedIn, Hartington]
  • A. Hartington chosen
    Hartington is a village and civil parish in Derbyshire, England, historically associated with the Cavendish family and the title Marquess of Hartington.
  • B. Lawhitton
    Lawhitton is a rural civil parish and village in Cornwall, England, known for its historic church and scenic countryside near the River Tamar.
  • C. Highton
    Highton is a residential suburb of Geelong in Victoria, Australia, known for its hilly terrain, family-friendly amenities, and views over the Barwon River.
  • D. Harvington
    Harvington is a village and civil parish in Worcestershire, England, known for its historic character and rural setting within the Wychavon district.
  • E. Hempton
    Hempton is a small village in Norfolk, England, situated close to the market town of Fakenham.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245836014819091b91ed3074742a3 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1615f63788190acf776b313f0794a completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 2:48 p.m.