Triple
T38677805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reb Saunders |
E943803
|
entity |
| Predicate | expectsFromSon |
P128116
|
FINISHED |
| Object | to succeed him as tzaddik |
—
|
LITERAL 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: to succeed him as tzaddik | Statement: [Reb Saunders, expectsFromSon, to succeed him as tzaddik]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectsFromSon Context triple: [Reb Saunders, expectsFromSon, to succeed him as tzaddik]
-
A.
expectsInheritanceFrom
Indicates that one entity anticipates or is intended to receive inheritance (such as assets, rights, or properties) from another entity.
-
B.
expectsEvent
Indicates that one entity anticipates, awaits, or is scheduled to receive the occurrence of a specific event.
-
C.
expectedBy
Indicates that one entity is anticipated, required, or relied upon by another as part of a plan, obligation, or dependency.
-
D.
holderExpectation
chosen
Indicates that one entity has an expectation, belief, or anticipated outcome regarding another entity or situation.
-
E.
subjectChildExpected
Indicates that the subject is expected or intended to have a child (or children), but the child has not yet been born or realized.
- F. None of above.
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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.