Triple

T17717957
Position Surface form Disambiguated ID Type / Status
Subject Schelle E442254 entity
Predicate locatedNear P294 FINISHED
Object Aartselaar 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: Aartselaar | Statement: [Schelle, locatedNear, Aartselaar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aartselaar
Context triple: [Schelle, locatedNear, Aartselaar]
  • A. Aartselaar chosen
    Aartselaar is a municipality in the Belgian province of Antwerp, known for its residential character and proximity to the city of Antwerp.
  • B. Roeselare
    Roeselare is a city in western Belgium known as an economic and commercial center in the province of West Flanders.
  • C. Borgerhout
    Borgerhout is a densely populated, multicultural district of the Belgian city of Antwerp, known for its vibrant street life and diverse communities.
  • D. Harelbeke
    Harelbeke is a municipality in the Belgian province of West Flanders, known for its historic town center and as a regular host of the E3 Saxo Bank Classic cycling race.
  • E. Lembeek
    Lembeek is a village in the Belgian municipality of Halle, located along the Senne River in the province of Flemish Brabant.
  • 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_69d8b9ec79688190b86bdcef85a7b3aa completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e474834aec81909ab7e8224c5a39d7 completed April 19, 2026, 6:21 a.m.
Created at: April 10, 2026, 10:06 a.m.