Triple

T21858599
Position Surface form Disambiguated ID Type / Status
Subject Haspengouw region E539697 entity
Predicate contains P35 FINISHED
Object Kortessem 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: Kortessem | Statement: [Haspengouw region, contains, Kortessem]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kortessem
Context triple: [Haspengouw region, contains, Kortessem]
  • A. Kortessem chosen
    Kortessem is a small municipality in the Belgian province of Limburg, known for its rural character and historic churches and castles.
  • B. Kaarsild
    Kaarsild is a pedestrian arch bridge in Tartu, Estonia, known for spanning the Emajõgi River and offering scenic views of the city.
  • C. Korsmo
    Korsmo is a surname most notably associated with Charlie Korsmo, a former child actor turned law professor.
  • D. Maselheim
    Maselheim is a rural municipality in the district of Biberach in the federal state of Baden-Württemberg in southern Germany.
  • E. Lessebo
    Lessebo is a small locality and municipality in southern Sweden known for its traditional paper mill and glassmaking heritage.
  • 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_69e0c47829648190bbe2d1d7033768ec completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f0d63944d88190b6bd5e6ba4cc8ec1 completed April 28, 2026, 3:46 p.m.
Created at: April 16, 2026, 6:56 p.m.