Triple

T8920344
Position Surface form Disambiguated ID Type / Status
Subject All Saints’ Church, Faringdon E212397 entity
Predicate locatedIn P40 FINISHED
Object Faringdon E212397 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: Faringdon | Statement: [All Saints’ Church, Faringdon, locatedIn, Faringdon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Faringdon
Context triple: [All Saints’ Church, Faringdon, locatedIn, Faringdon]
  • A. Faringdon chosen
    Faringdon is a historic market town in Oxfordshire, England, known for its medieval church, traditional market square, and nearby Faringdon Folly tower.
  • B. Stonesfield
    Stonesfield is a rural village in Oxfordshire, England, known historically for its Cotswold stone quarries and scenic countryside setting.
  • C. Freckenham
    Freckenham is a small rural village and civil parish located in the English county of Suffolk.
  • D. Farningham
    Farningham is a historic village in the Sevenoaks District of Kent, England, known for its rural character and location on the River Darent.
  • E. Fairford
    Fairford is a small market town in Gloucestershire, England, known for its historic wool church and proximity to RAF Fairford airbase.
  • 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_69ca839481d48190b42b037e0d0f636c completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc664f099c8190be6d20a4574212ca completed April 1, 2026, 12:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfc932f9848190a2571cfc28353088 completed April 3, 2026, 2:05 p.m.
Created at: March 30, 2026, 6:56 p.m.