Triple

T18441843
Position Surface form Disambiguated ID Type / Status
Subject Lodewijk van Heiden E450547 entity
Predicate givenName P17 FINISHED
Object Lodewijk 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: Lodewijk | Statement: [Lodewijk van Heiden, givenName, Lodewijk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lodewijk
Context triple: [Lodewijk van Heiden, givenName, Lodewijk]
  • A. Lodewijk chosen
    Lodewijk is the Dutch given name equivalent to Ludwig, historically borne by several notable figures including Dutch nobles and artists.
  • B. Lodewijk van Heiden
    Lodewijk van Heiden was a Dutch-born admiral in the Imperial Russian Navy, best known for his key role in the decisive Allied victory at the Battle of Navarino during the Greek War of Independence.
  • C. Lubbertus
    Lubbertus is a Dutch surname most notably associated with the Reformed theologian Sibrandus Lubbertus of the late 16th and early 17th centuries.
  • D. Lodewijk de Vadder
    Lodewijk de Vadder was a 17th-century Flemish Baroque landscape painter and engraver known for his atmospheric depictions of wooded scenes and dunes around Brussels.
  • E. Adriaan
    Adriaan is a masculine given name of Dutch origin commonly used in the Netherlands and other Dutch-speaking regions.
  • 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_69d8d381d6388190a9e94e9c658174e4 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e51c11b1288190b9ed4497751197d1 completed April 19, 2026, 6:16 p.m.
Created at: April 10, 2026, 11:30 a.m.