Triple

T21438213
Position Surface form Disambiguated ID Type / Status
Subject Prince Aschwin of Lippe-Biesterfeld E528869 entity
Predicate givenName P17 FINISHED
Object Aschwin 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: Aschwin | Statement: [Prince Aschwin of Lippe-Biesterfeld, givenName, Aschwin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aschwin
Context triple: [Prince Aschwin of Lippe-Biesterfeld, givenName, Aschwin]
  • A. Aschwin chosen
    Aschwin is a masculine given name of Germanic origin, used in various European countries.
  • B. Sjaalman
    Sjaalman is a fictional character in Multatuli’s novel "Max Havelaar," serving as an alter ego and narrative device to expose colonial abuses in the Dutch East Indies.
  • C. Andries
    Andries is a Dutch given name traditionally used for men, equivalent to Andrew in English.
  • D. Arnish
    Arnish is a small village located on the Isle of Raasay in the Inner Hebrides of Scotland.
  • E. Ockenga
    Ockenga is a surname most notably associated with Harold Ockenga, a prominent American evangelical leader and theologian.
  • 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_69e0c4569fa081908101baa24f8745db completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e8b53972e48190bc8bbc543173854c completed April 22, 2026, 11:47 a.m.
Created at: April 16, 2026, 6:04 p.m.