Triple

T35738337
Position Surface form Disambiguated ID Type / Status
Subject Moshe Sofer E1032956 entity
Predicate student P7251 FINISHED
Object Hillel Lichtenstein
Hillel Lichtenstein was a prominent 19th-century Hungarian Orthodox rabbi and leader of the ultra-traditionalist movement opposing religious reform within Judaism.
E2287366 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: Hillel Lichtenstein | Statement: [Moshe Sofer, student, Hillel Lichtenstein]
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: Hillel Lichtenstein
Triple: [Moshe Sofer, student, Hillel Lichtenstein]
Generated description
Hillel Lichtenstein was a prominent 19th-century Hungarian Orthodox rabbi and leader of the ultra-traditionalist movement opposing religious reform within Judaism.

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_69f76e10e59081908d81ad9ce22f40b6 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a168b33081909e20588b6c65ac6d completed May 3, 2026, 7:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a47823b95e0819090f4c8e7ad9b5998 completed July 3, 2026, 9:34 a.m.
NEDg Description generation batch_6a47839c314c819081caf9228012bab2 completed July 3, 2026, 9:40 a.m.
NED2 Entity disambiguation (via description) batch_6a4784092e408190abf0b8d753264a40 completed July 3, 2026, 9:42 a.m.
Created at: May 3, 2026, 4:05 p.m.