Triple

T19979607
Position Surface form Disambiguated ID Type / Status
Subject Æthelmar E493780 entity
Predicate placeOfActivity P1527 FINISHED
Object Eynsham 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: Eynsham | Statement: [Æthelmar, placeOfActivity, Eynsham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eynsham
Context triple: [Æthelmar, placeOfActivity, Eynsham]
  • A. Eynsham chosen
    Eynsham is a historic village in Oxfordshire, England, known for its medieval abbey remains and its location near the River Thames between Oxford and Witney.
  • B. Shiplake
    Shiplake is a village in Oxfordshire, England, situated near the River Thames close to Henley-on-Thames.
  • C. Pangbourne
    Pangbourne is a picturesque village on the River Thames in Berkshire, England, known for its literary associations and scenic rural charm.
  • D. Shrivenham
    Shrivenham is a village in Oxfordshire, England, known for its historic high street, rural setting, and association with nearby military and academic institutions.
  • E. Moretonhampstead
    Moretonhampstead is a historic market town on the edge of Dartmoor in Devon, England, known for its picturesque setting and traditional architecture.
  • 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_69da626a67648190af9653832a3aeced completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e65d11d2108190bd1d91fdc834888b completed April 20, 2026, 5:06 p.m.
Created at: April 11, 2026, 3:27 p.m.