Triple

T14021539
Position Surface form Disambiguated ID Type / Status
Subject Dormansland E337342 entity
Predicate locatedNear P294 FINISHED
Object Lingfield E17308 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: Lingfield | Statement: [Dormansland, locatedNear, Lingfield]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lingfield
Context triple: [Dormansland, locatedNear, Lingfield]
  • A. Lingfield chosen
    Lingfield is a village and civil parish in the Tandridge district of Surrey, England, known for its historic buildings and Lingfield Park Racecourse.
  • B. Oundle
    Oundle is a historic market town in Northamptonshire, England, known for its traditional stone architecture and the prestigious Oundle School.
  • C. Kempton Park
    Kempton Park is a town on the East Rand in Gauteng, South Africa, known for housing OR Tambo International Airport and being part of the greater Johannesburg metropolitan area.
  • D. Kempton
    Kempton is a surname most notably associated with Murray Kempton, an influential American journalist and social commentator.
  • E. Lambourn
    Lambourn is a large village and civil parish in Berkshire, England, best known as a major center for British racehorse training in the Lambourn Downs.
  • 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_69d81c6543a48190bd5ba93d7419e797 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2f3c7cd88190b236382058581740 completed April 14, 2026, 12:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcb655bb34819097fe88ba76464be8 completed May 7, 2026, 3:57 p.m.
Created at: April 9, 2026, 10:19 p.m.