Triple

T22413708
Position Surface form Disambiguated ID Type / Status
Subject Megen, Haren en Macharen E554057 entity
Predicate containsSettlement P847 FINISHED
Object Haren 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: Haren | Statement: [Megen, Haren en Macharen, containsSettlement, Haren]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Haren
Context triple: [Megen, Haren en Macharen, containsSettlement, Haren]
  • A. Haren
    Haren is a district in the northern part of Brussels, Belgium, known for its mix of residential areas, industrial zones, and transport infrastructure.
  • B. Haren chosen
    Haren is a village in the Netherlands that functions as a submunicipality within the municipality of Oss in the province of North Brabant.
  • C. Harenc
    Harenc was a medieval fortress town in northern Syria that played a strategic role during the Crusades.
  • D. Hearn
    Hearn is a surname of English and Irish origin borne by various notable individuals across fields such as sports, entertainment, and literature.
  • E. Heren
    Heren is a traditional folk dance of the Dogra people, reflecting their cultural heritage and regional customs.
  • 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_69e11e4e6ce8819085a1e06d886bf21c completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1594496348190ba25dc0193d092f2 completed April 29, 2026, 1:05 a.m.
Created at: April 16, 2026, 8:46 p.m.