Triple

T11243475
Position Surface form Disambiguated ID Type / Status
Subject Lennart E266135 entity
Predicate hasVariantSpelling P457 FINISHED
Object Lennert E673512 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: Lennert | Statement: [Lennart, hasVariantSpelling, Lennert]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lennert
Context triple: [Lennart, hasVariantSpelling, Lennert]
  • A. Lennertz
    Lennertz is a German-origin surname borne by various individuals, including American composer Christopher Lennertz.
  • B. Leendert chosen
    Leendert is a Dutch masculine given name, notably borne by mathematician Bartel Leendert van der Waerden.
  • C. Roy Leenig
    Roy Leenig was a prominent American college basketball coach best known for his successful tenure leading the Holy Cross Crusaders men's basketball program.
  • D. Lourens
    Lourens is a given name derived from the Latin name Laurentius, commonly used in Dutch and Afrikaans contexts.
  • E. Leonardo Zeevaert
    Leonardo Zeevaert was a prominent Mexican civil and structural engineer renowned for pioneering earthquake-resistant design and foundation engineering in Mexico.
  • 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_69d6aac656d48190b275efaa7d6074ee completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e91b0b808190bc38008bb344d180 completed April 9, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4ad849f70819098a7056fbc4831ff completed April 19, 2026, 10:25 a.m.
Created at: April 8, 2026, 9:30 p.m.