Triple

T18955053
Position Surface form Disambiguated ID Type / Status
Subject Audlem Locks E463749 entity
Predicate locatedIn P40 FINISHED
Object Audlem 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: Audlem | Statement: [Audlem Locks, locatedIn, Audlem]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Audlem
Context triple: [Audlem Locks, locatedIn, Audlem]
  • A. Audlem chosen
    Audlem is a picturesque village and civil parish in Cheshire, England, known for its historic buildings, canal locks, and rural charm.
  • B. Asthall
    Asthall is a small historic village in Oxfordshire, England, known for its Cotswold stone architecture and association with the Mitford family.
  • C. Alvediston
    Alvediston is a small rural village in Wiltshire, England, known for its historic manor house and picturesque countryside setting.
  • D. Minstead
    Minstead is a small village in Hampshire, England, best known as the burial place of Sir Arthur Conan Doyle.
  • E. Simmondley
    Simmondley is a village in Derbyshire, England, situated within the High Peak district and known for its semi-rural setting near the town of Glossop.
  • 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_69d8dcffc278819086792a4ebfddfafa completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d546babc81909d4fc5b6b4441aac completed April 20, 2026, 7:27 a.m.
Created at: April 10, 2026, noon