Triple

T18877304
Position Surface form Disambiguated ID Type / Status
Subject Aylestone E461720 entity
Predicate hasPart P35 FINISHED
Object Aylestone Village 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: Aylestone Village | Statement: [Aylestone, hasPart, Aylestone Village]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aylestone Village
Context triple: [Aylestone, hasPart, Aylestone Village]
  • A. Aylestone chosen
    Aylestone is a suburban area of Leicester, England, known for its historic village core and riverside setting along the River Soar.
  • B. Doyleston
    Doyleston is a small rural settlement in the Canterbury region of New Zealand’s South Island.
  • C. Longwell Green
    Longwell Green is a suburban area and civil parish in South Gloucestershire, England, situated on the eastern outskirts of Bristol.
  • D. Talbot Village
    Talbot Village is a residential suburb in the Poole–Bournemouth urban area on England’s south coast, known for its mix of historic village character and proximity to local universities.
  • E. Edwardstone village
    Edwardstone village is a small rural community in Suffolk, England, known for its historic parish church, traditional countryside character, and surrounding farmland.
  • 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_69d8dcfc3430819095ee6fc0eb4c06a5 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c3cf0aa0819090991fc9e14910fb completed April 20, 2026, 6:12 a.m.
Created at: April 10, 2026, 11:57 a.m.