Triple

T10632797
Position Surface form Disambiguated ID Type / Status
Subject Ruxley Gravel Pits E250500 entity
Predicate locatedIn P40 FINISHED
Object Ruxley E250500 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: Ruxley | Statement: [Ruxley Gravel Pits, locatedIn, Ruxley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ruxley
Context triple: [Ruxley Gravel Pits, locatedIn, Ruxley]
  • A. Ruxley chosen
    Ruxley is a locality in the London Borough of Bromley, England, known for its mix of suburban development and nearby nature reserves such as the Ruxley Gravel Pits.
  • B. Northbourne
    Northbourne is a small village and civil parish in Kent, England, known for its rural character and historic church.
  • C. Hordley
    Hordley is a small rural settlement located in the parish of St. Thomas in the East, Jamaica.
  • D. Rushworth
    Rushworth is the middle name of Lord Jellicoe, a British naval officer and statesman who served as First Sea Lord during World War I.
  • E. Rushworth
    Rushworth is a small rural town in northern Victoria, Australia, known for its gold rush heritage and historic streetscape.
  • 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_69d6aa5993448190a493b790b8f85010 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6df95f5e88190b34ce3ec972759ef completed April 8, 2026, 11:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69d96bbd64d8819089d55af875d39e45 completed April 10, 2026, 9:29 p.m.
Created at: April 8, 2026, 9:02 p.m.