Triple

T13984543
Position Surface form Disambiguated ID Type / Status
Subject Friedrich Bonte E336402 entity
Predicate familyName P18 FINISHED
Object Bonte E336402 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: Bonte | Statement: [Friedrich Bonte, familyName, Bonte]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bonte
Context triple: [Friedrich Bonte, familyName, Bonte]
  • A. Bonte chosen
    Bonte is a German surname most notably borne by Friedrich Bonte, a Kriegsmarine officer during World War II.
  • B. De Bolle
    De Bolle is the surname of Catherine De Bolle, a prominent Belgian police official and former Executive Director of Europol.
  • C. Stroobos
    Stroobos is a small village in the northern Netherlands, situated on the border of Friesland and Groningen and known for its location along important waterways and canals.
  • D. Berte
    Berte is a minor character in Henrik Ibsen’s play "Hedda Gabler," serving as the Tesmans’ maid and highlighting the household’s social dynamics.
  • E. Beerta
    Beerta is a village in the municipality of Oldambt in the province of Groningen in the northeastern Netherlands.
  • 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_69d81c639e808190a0e4b4f3d31c6a59 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2ea3e5a081908ed8ead108139252 completed April 14, 2026, 12:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69fbac942ba481908858d7f214085b5f completed May 6, 2026, 9:03 p.m.
Created at: April 9, 2026, 10:18 p.m.