Triple
T23669756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebbe of Sanz |
E584696
|
entity |
| Predicate | expectedToExemplify |
P128116
|
FINISHED |
| Object | devotion to Torah study |
—
|
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: devotion to Torah study | Statement: [Rebbe of Sanz, expectedToExemplify, devotion to Torah study]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedToExemplify Context triple: [Rebbe of Sanz, expectedToExemplify, devotion to Torah study]
-
A.
isSupposedToBe
Indicates that something is expected or intended to have a particular state, quality, or role, whether or not it actually does.
-
B.
holderExpectation
chosen
Indicates that one entity has an expectation, belief, or anticipated outcome regarding another entity or situation.
-
C.
exhortedTo
Indicates that one entity strongly urged, encouraged, or pressured another entity to perform a particular action or adopt a certain course of behavior.
-
D.
demonstratedBy
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
-
E.
demonstratesTo
Indicates that one entity actively shows, explains, or proves something to another entity.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b40dc0ec8190b558e30dbebf491f |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.