Triple

T24198654
Position Surface form Disambiguated ID Type / Status
Subject Speiser E599906 entity
Predicate hasNotableBearer P458 FINISHED
Object Shmuel Speiser
Shmuel Speiser was a prominent 20th-century Assyriologist and biblical scholar known for his influential work on ancient Near Eastern languages and the Book of Genesis.
E1630184 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: Shmuel Speiser | Statement: [Speiser, hasNotableBearer, Shmuel Speiser]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Shmuel Speiser
Triple: [Speiser, hasNotableBearer, Shmuel Speiser]
Generated description
Shmuel Speiser was a prominent 20th-century Assyriologist and biblical scholar known for his influential work on ancient Near Eastern languages and the Book of Genesis.

Provenance (5 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_69e288ceaab88190899d0acb5931591d completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f27c9f61f881909f7e1287388ff982 completed April 29, 2026, 9:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0fd63f16088190ac48ffe18147fa18 completed May 22, 2026, 4:06 a.m.
NEDg Description generation batch_6a0fd7124c4481908d899a9292f534e9 completed May 22, 2026, 4:09 a.m.
NED2 Entity disambiguation (via description) batch_6a0fd7c16e788190a760642a991c421e completed May 22, 2026, 4:12 a.m.
Created at: April 17, 2026, 11:36 p.m.