Triple

T13775502
Position Surface form Disambiguated ID Type / Status
Subject Saint-Josse-ten-Noode E330994 entity
Predicate locatedNextTo P231 FINISHED
Object Schaerbeek E363736 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: Schaerbeek | Statement: [Saint-Josse-ten-Noode, locatedNextTo, Schaerbeek]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schaerbeek
Context triple: [Saint-Josse-ten-Noode, locatedNextTo, Schaerbeek]
  • A. Schaerbeek chosen
    Schaerbeek is a multicultural municipality in the Brussels-Capital Region of Belgium, known for its Art Nouveau architecture and urban character.
  • B. Bellebeek
    Bellebeek is a small stream in Belgium that serves as a right-bank tributary of the River Dender.
  • C. Diepenbeek
    Diepenbeek is a municipality in the Belgian province of Limburg, known for its blend of residential areas, industry, and the campus of Hasselt University.
  • D. Brussel-Zuid
    Brussel-Zuid is the main international and one of the busiest railway stations in Brussels, serving high-speed and regional trains including Eurostar and Thalys services.
  • E. Edegem
    Edegem is a municipality in the Belgian province of Antwerp, known as a residential suburb south of the city of Antwerp.
  • 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_69d81c583b0081909e408a17db517a21 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de0238bdbc8190a946e6e5431632a5 completed April 14, 2026, 9 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7a86afd788190ab637044dd489a24 completed May 3, 2026, 7:56 p.m.
Created at: April 9, 2026, 10:10 p.m.