Triple

T23294011
Position Surface form Disambiguated ID Type / Status
Subject Battle of Lansdowne E590112 entity
Predicate location P40 FINISHED
Object Lansdown Hill 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: Lansdown Hill | Statement: [Battle of Lansdowne, location, Lansdown Hill]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lansdown Hill
Context triple: [Battle of Lansdowne, location, Lansdown Hill]
  • A. Beeston Hill
    Beeston Hill is a residential area forming part of the wider Beeston district in the south of Leeds, West Yorkshire, England.
  • B. Pound Hill
    Pound Hill is a residential neighbourhood and one of the main suburban areas within the town of Crawley in West Sussex, England.
  • C. Chinthurst Hill
    Chinthurst Hill is a wooded hill and local beauty spot near Wonersh in Surrey, England, known for its scenic views and walking trails.
  • D. Portsdown Hill
    Portsdown Hill is a long chalk ridge in Hampshire, England, overlooking the city of Portsmouth and the Solent, known for its panoramic views and historic military fortifications.
  • E. Lansdown chosen
    Lansdown is a district of Cheltenham in Gloucestershire, England, known for its Regency architecture and residential character.
  • 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_69e25d1af9d88190a0b9b5e8fa608618 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f196cdce7081908ca1cf9107b87f61 completed April 29, 2026, 5:27 a.m.
Created at: April 17, 2026, 5:02 p.m.