Triple

T22564612
Position Surface form Disambiguated ID Type / Status
Subject D14 (Eexterhalte hunebed) E557912 entity
Predicate locatedIn P40 FINISHED
Object Eexterhalte 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: Eexterhalte | Statement: [D14 (Eexterhalte hunebed), locatedIn, Eexterhalte]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eexterhalte
Context triple: [D14 (Eexterhalte hunebed), locatedIn, Eexterhalte]
  • A. Extertal
    Extertal is a municipality in the Lippe district of North Rhine-Westphalia, Germany, known for its rural landscape and small villages in the Weser Uplands region.
  • B. Eexterveen chosen
    Eexterveen is a small village in the Dutch province of Drenthe, located within the municipality of Borger-Odoorn.
  • C. Ekster
    Ekster is the surname of Alexandra Exter, a prominent Russian-Ukrainian avant-garde painter and stage designer associated with Cubism and Futurism.
  • D. Exter
    Exter is a village and district of the town of Vlotho in the German state of North Rhine-Westphalia.
  • E. Ehlhalten
    Ehlhalten is a village and district of the town of Eppstein in the Rheingau-Taunus region of Hesse, Germany.
  • 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_69e11e5ae4ac8190b1f503457603d969 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15fa8d8388190856198547d56dce6 completed April 29, 2026, 1:32 a.m.
Created at: April 16, 2026, 8:52 p.m.