Triple

T17701743
Position Surface form Disambiguated ID Type / Status
Subject Church of St James, Sarsden E441320 entity
Predicate locatedIn P40 FINISHED
Object Sarsden 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: Sarsden | Statement: [Church of St James, Sarsden, locatedIn, Sarsden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sarsden
Context triple: [Church of St James, Sarsden, locatedIn, Sarsden]
  • A. Sarsden chosen
    Sarsden is a small rural village in Oxfordshire, England, known for its historic manor house and picturesque countryside setting.
  • B. Southdene
    Southdene is a residential area and suburb located near the town of Kirkby in Merseyside, England.
  • C. Screveton
    Screveton is a small rural village and civil parish in Nottinghamshire, England, known for its historic church and traditional countryside character.
  • D. Tesseney
    Tesseney is a town in western Eritrea near the Sudanese border, serving as a local commercial and agricultural center in the Gash-Barka region.
  • E. Sandarne
    Sandarne is a small locality in east-central Sweden, situated on the coast within Gävleborg County.
  • 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_69d8b9ea20b48190ace88bb46b01e6a9 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4715c3980819094b080a871df1100 completed April 19, 2026, 6:08 a.m.
Created at: April 10, 2026, 10:04 a.m.