Triple

T22565494
Position Surface form Disambiguated ID Type / Status
Subject Frederiksoord E557937 entity
Predicate hasNearbyColony P148757 FINISHED
Object Boschoord 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: Boschoord | Statement: [Frederiksoord, hasNearbyColony, Boschoord]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Boschoord
Context triple: [Frederiksoord, hasNearbyColony, Boschoord]
  • A. Boschoord chosen
    Boschoord is a small village in the Dutch province of Drenthe, known for its rural setting and surrounding natural landscapes.
  • B. Wijbosch
    Wijbosch is a village in the Dutch province of North Brabant, located within the municipality of Meierijstad.
  • C. Wiekevorst
    Wiekevorst is a village in the Belgian province of Antwerp that forms part of the municipality of Heist-op-den-Berg.
  • D. Kolderbos
    Kolderbos is a residential district of the Belgian city of Genk, known for its post-war social housing and multicultural community.
  • E. Boesinghe
    Boesinghe is a village in West Flanders, Belgium, known for its proximity to key World War I battlefields along the Yser Front.
  • 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_69f15fa9ebc8819098d74fb41e14bd7e completed April 29, 2026, 1:32 a.m.
Created at: April 16, 2026, 8:52 p.m.