Triple

T22997710
Position Surface form Disambiguated ID Type / Status
Subject Johan August von Essen E572546 entity
Predicate familyName P18 FINISHED
Object von Essen 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: von Essen | Statement: [Johan August von Essen, familyName, von Essen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: von Essen
Context triple: [Johan August von Essen, familyName, von Essen]
  • A. von Essen chosen
    Von Essen is a Swedish noble family name historically associated with figures in Scandinavian arts and society.
  • B. von Schlieben
    von Schlieben is a German noble family name historically associated with military officers and aristocracy.
  • C. Eschen
    Eschen is a municipality in northern Liechtenstein known for its residential character and role as one of the country’s larger population centers.
  • D. Erasbach
    Erasbach is a small locality in Bavaria, Germany, best known as the birthplace of the composer Christoph Willibald Gluck.
  • E. Schehring
    Schehring is an alternative spelling or variant name of Schering, a historic German pharmaceutical and chemical company known for its contributions to medicine and life sciences.
  • 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_69e245b6a3ac81908087599eefe3e365 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f182f452b48190951fc5dde56c1bb2 completed April 29, 2026, 4:03 a.m.
Created at: April 17, 2026, 3:50 p.m.