Triple

T12341998
Position Surface form Disambiguated ID Type / Status
Subject Van Amsberg E294249 entity
Predicate spellingVariant P457 FINISHED
Object von Amsberg E294249 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: von Amsberg | Statement: [Van Amsberg, spellingVariant, von Amsberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: von Amsberg
Context triple: [Van Amsberg, spellingVariant, von Amsberg]
  • A. van Amsberg chosen
    Van Amsberg is the German-origin noble family name associated with the Dutch royal family, including members such as Prince Constantijn of the Netherlands.
  • B. von Schlebrügge
    von Schlebrügge is the aristocratic German-Swedish family name of Nena von Schlebrügge, a former fashion model and mother of actress Uma Thurman.
  • C. von Kühn
    von Kühn is a German noble family name historically associated with figures such as Sophie von Kühn.
  • D. von Holzhausen
    von Holzhausen is a German-origin surname historically associated with several notable figures, including contemporary automotive designer Franz von Holzhausen.
  • E. von Osten
    Von Osten is a German noble family name historically associated with Baltic and Prussian aristocracy.
  • 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_69d6ab6ccbec8190b09e2d357aa80064 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d93f7758dc8190bbc6a9ad00b01dce completed April 10, 2026, 6:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6346dd09481908f4c80e89e2f4705 completed May 2, 2026, 5:29 p.m.
Created at: April 8, 2026, 9:53 p.m.