Triple

T35574383
Position Surface form Disambiguated ID Type / Status
Subject Brenninkmeijer family E1028033 entity
Predicate foundingLocationAssociated P55364 FINISHED
Object Sneek 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: Sneek | Statement: [Brenninkmeijer family, foundingLocationAssociated, Sneek]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: foundingLocationAssociated
Context triple: [Brenninkmeijer family, foundingLocationAssociated, Sneek]
  • A. foundingLocationOfFoundedOrganization chosen
    Indicates the place where an organization was originally established or founded.
  • B. foundingLocationPresentCountry
    Indicates the present-day country in which the location where something (typically an organization or institution) was founded is situated.
  • C. locatedInCityFoundedFor
    Indicates that something is located in a city that was specifically founded for that thing or for its primary purpose.
  • D. foundedNear
    Indicates that one entity established or created another entity at a location geographically close to a specified reference entity or place.
  • E. coFoundedIn
    Indicates that two or more entities jointly founded something (such as an organization or company) in a specific place or at a specific time.
  • F. None of above.

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_69f76e0386688190b931bacdc145938c completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69feff70fbec8190b1ff5f943f29613e completed May 9, 2026, 9:33 a.m.
PD Predicate disambiguation batch_69fefbcd5b7881909cfe52b32f8a4301 completed May 9, 2026, 9:18 a.m.
Created at: May 3, 2026, 4:04 p.m.