Triple

T12305724
Position Surface form Disambiguated ID Type / Status
Subject Stulpkerk, Lage Vuursche, Netherlands E293346 entity
Predicate locatedIn P40 FINISHED
Object Lage Vuursche E481214 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: Lage Vuursche | Statement: [Stulpkerk, Lage Vuursche, Netherlands, locatedIn, Lage Vuursche]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lage Vuursche
Context triple: [Stulpkerk, Lage Vuursche, Netherlands, locatedIn, Lage Vuursche]
  • A. Lage Vuursche chosen
    Lage Vuursche is a small, historic village in the Dutch province of Utrecht, known for its forests, royal estate nearby, and popular pancake restaurants.
  • B. Vantongerloo
    Vantongerloo is the surname of Georges Vantongerloo, a Belgian abstract artist and sculptor associated with the De Stijl movement.
  • C. Boesinghe
    Boesinghe is a village in West Flanders, Belgium, known for its proximity to key World War I battlefields along the Yser Front.
  • D. Lage Zwaluwe
    Lage Zwaluwe is a village in the Dutch province of North Brabant, known for its proximity to the Biesbosch National Park and its railway connections.
  • E. Lodewijck
    Lodewijck is a Dutch given name, an older or variant spelling of Lodewijk, equivalent to the English name Louis.
  • 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_69d6ab6a2b50819082f6aedd32ed608a completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d93f00695c8190b7365e4593631690 completed April 10, 2026, 6:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69f61e7f8fd08190bdef3bb761d53f97 completed May 2, 2026, 3:55 p.m.
Created at: April 8, 2026, 9:53 p.m.