Triple

T20885306
Position Surface form Disambiguated ID Type / Status
Subject Oldambt E514261 entity
Predicate contains P35 FINISHED
Object Noordbroek 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: Noordbroek | Statement: [Oldambt, contains, Noordbroek]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Noordbroek
Context triple: [Oldambt, contains, Noordbroek]
  • A. Noordbroek chosen
    Noordbroek is a village in the Dutch province of Groningen, known for its historic church and rural character.
  • B. Westerbroek
    Westerbroek is a village in the Dutch province of Groningen, known for its rural character and surrounding peat and nature areas.
  • C. Bredevoort
    Bredevoort is a small historic town in the Dutch province of Gelderland, known for its well-preserved medieval character and its reputation as a national "book town."
  • D. Brinkhorst
    Brinkhorst is the Dutch family name of Princess Laurentien of the Netherlands, associated with a prominent political and aristocratic lineage.
  • E. Zonnemaire
    Zonnemaire is a small village in the Dutch province of Zeeland, notable as the birthplace of Nobel Prize–winning physicist Pieter Zeeman.
  • 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_69e0b4f733f081908a401c0b7beb0b9f completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c67c9d1c81908031eb77c124f119 completed April 21, 2026, 12:36 a.m.
Created at: April 16, 2026, 12:46 p.m.