Triple

T8864286
Position Surface form Disambiguated ID Type / Status
Subject Benjamin Earl Nelson E210974 entity
Predicate givenName P17 FINISHED
Object Benjamin E342186 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: Benjamin | Statement: [Benjamin Earl Nelson, givenName, Benjamin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Benjamin
Context triple: [Benjamin Earl Nelson, givenName, Benjamin]
  • A. Benjamin
    Benjamin is the given name of the 20th-century Lithuanian-born American artist and social realist Ben Shahn.
  • B. Benjamin chosen
    Benjamin is a masculine given name of Hebrew origin meaning "son of the right hand" or "favored son," widely used in many cultures and languages.
  • C. Benjamin
    Benjamin is the naive, dream-filled protagonist of Mendele Mocher Sforim’s satirical Yiddish novel "The Travels of Benjamin the Third," often likened to a Jewish Don Quixote.
  • D. Benjamin
    Benjamin is the full given name of the English playwright and poet Ben Jonson, a major literary figure of the early 17th century.
  • E. Benjamin
    Benjamin is a surname of Hebrew origin commonly used in many cultures and languages.
  • 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_69ca838d3c7c8190a849566d5afd2b11 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc610569d08190b108107dfe397f18 completed April 1, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfab9764388190a57ca0c0bb890523 completed April 3, 2026, 11:59 a.m.
Created at: March 30, 2026, 6:51 p.m.