Triple

T4233031
Position Surface form Disambiguated ID Type / Status
Subject Daniel Heinsius E94624 entity
Predicate familyName P18 FINISHED
Object Heinsius E94624 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: Heinsius | Statement: [Daniel Heinsius, familyName, Heinsius]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heinsius
Context triple: [Daniel Heinsius, familyName, Heinsius]
  • A. Heinsius chosen
    Heinsius is a Dutch surname most notably associated with Anthonie Heinsius, a prominent statesman of the Dutch Republic in the late 17th and early 18th centuries.
  • B. Finsch
    Finsch is the authority who first formally described the Fiordland crested penguin in the scientific literature.
  • C. de Heister
    De Heister is a German noble family name historically associated with military officers and aristocrats, including the Hessian general Leopold Philip de Heister.
  • D. Ozinga
    Ozinga is a Dutch surname most notably associated with individuals such as Sjoukje Ozinga.
  • E. Nitibe
    Nitibe is an administrative post and rural area within the Oecusse exclave of Timor-Leste, known for its coastal and agricultural communities.
  • 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_69b34537cc6481909cd0a96acbb33ef7 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34e65720c819087c4022c774ff7c3 completed March 12, 2026, 11:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5b77632d08190ab7c12986e2cee61 completed March 14, 2026, 7:31 p.m.
Created at: March 12, 2026, 11:05 p.m.