Triple

T13487166
Position Surface form Disambiguated ID Type / Status
Subject Moses Asch E318534 entity
Predicate familyName P18 FINISHED
Object Asch E318526 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: Asch | Statement: [Moses Asch, familyName, Asch]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Asch
Context triple: [Moses Asch, familyName, Asch]
  • A. Asch chosen
    Asch is a surname most notably associated with Sholem Asch, a prominent Polish-Jewish novelist and playwright of the early 20th century.
  • B. Abelson
    Abelson is a surname most notably associated with Hal Abelson, an American computer scientist and educator known for his work on the Scheme programming language and the textbook "Structure and Interpretation of Computer Programs."
  • C. Ehrenstein
    Ehrenstein is a locality or district that forms part of the municipality of Blaustein in the state of Baden-Württemberg, Germany.
  • D. Blumer
    Blumer is the surname of Herbert Blumer, an influential American sociologist known for developing the theory of symbolic interactionism.
  • E. Loewenstein
    Loewenstein is a surname of German origin associated with various notable individuals in fields such as science, politics, and the arts.
  • 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_69d806b6bfec819089222715b2e86c8e completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaf3b9b488190bb4e11424ff599c8 completed April 12, 2026, 2:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69f75483a6f88190b3815fb8d97e65e4 completed May 3, 2026, 1:58 p.m.
Created at: April 9, 2026, 9:42 p.m.