Triple

T22160219
Position Surface form Disambiguated ID Type / Status
Subject East Preston E547647 entity
Predicate near P350 FINISHED
Object Angmering 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: Angmering | Statement: [East Preston, near, Angmering]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Angmering
Context triple: [East Preston, near, Angmering]
  • A. Angmering chosen
    Angmering is a large village and civil parish in the Arun district of West Sussex, England, situated between Littlehampton and Worthing near the south coast.
  • B. Birkholm
    Birkholm is a small, sparsely populated Danish island known for its tranquil natural environment and traditional village atmosphere in the South Funen Archipelago.
  • C. Altomünster
    Altomünster is a market town in Upper Bavaria, Germany, known for its historic monastery and rural Bavarian character.
  • D. Baumberge
    Baumberge is a low mountain and hill range in the Münsterland region of North Rhine-Westphalia, Germany, known for its forests, hiking trails, and scenic landscapes.
  • E. Willadingen
    Willadingen is a small Swiss village located in the Emmental region of the canton of Bern.
  • 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_69e11e3c4c5c81908d336165816b12e0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12a2c17a4819082fb9e4aaa275462 completed April 28, 2026, 9:44 p.m.
Created at: April 16, 2026, 8:33 p.m.