Triple

T19562065
Position Surface form Disambiguated ID Type / Status
Subject Charles Ruijs de Beerenbrouck E489476 entity
Predicate nobleTitle P914 FINISHED
Object Jonkheer 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: Jonkheer | Statement: [Charles Ruijs de Beerenbrouck, nobleTitle, Jonkheer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jonkheer
Context triple: [Charles Ruijs de Beerenbrouck, nobleTitle, Jonkheer]
  • A. Jonkheer chosen
    Jonkheer is a Dutch hereditary honorific used for members of the untitled lower nobility in the Netherlands and Belgium.
  • B. Jonkheer von Amsberg
    Jonkheer von Amsberg is a Dutch noble title historically associated with the German-born Claus von Amsberg, who became Prince Claus of the Netherlands through his marriage to Queen Beatrix.
  • C. Baron Shingay
    Baron Shingay is a hereditary title in the Peerage of England historically associated with the Russell family, notably held by Edward Russell, 1st Earl of Orford.
  • D. Baron
    Baron is a hereditary rank of nobility typically positioned below a viscount or count in European aristocratic hierarchies.
  • E. Duke of Nysa
    Duke of Nysa was a noble title in the Polish–Lithuanian Commonwealth associated with the Vasa dynasty, notably held by Prince Charles Ferdinand Vasa.
  • 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63f74fdb08190852461b5d5c954ac completed April 20, 2026, 3 p.m.
Created at: April 10, 2026, 1:42 p.m.