Triple

T12042499
Position Surface form Disambiguated ID Type / Status
Subject Heinrich Lenz E286696 entity
Predicate familyName P18 FINISHED
Object Lenz E841991 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: Lenz | Statement: [Heinrich Lenz, familyName, Lenz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lenz
Context triple: [Heinrich Lenz, familyName, Lenz]
  • A. Lenz chosen
    Lenz is a German surname most notably associated with the 18th-century Sturm und Drang writer Jakob Michael Reinhold Lenz.
  • B. Lentz
    Lentz is a surname most notably associated with Irene Lentz, an influential American fashion and costume designer in Hollywood’s Golden Age.
  • C. Gouy
    Gouy is a small commune in northern France located within the administrative boundaries of the canton of Le Cateau-Cambrésis.
  • D. Lindemann
    Lindemann is a German surname most notably associated with Ferdinand von Lindemann, the mathematician who proved that π is a transcendental number.
  • E. Néel
    Néel is a French surname most notably associated with physicist Louis Néel, a Nobel laureate recognized for his pioneering work in magnetism.
  • 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_69d6ab4780948190bdb9f7620c2ac27e completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9040d13108190bd1a969fa62aae5a completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f49da728ec819080c349fd8d0ed62c completed May 1, 2026, 12:33 p.m.
Created at: April 8, 2026, 9:47 p.m.