Triple
T5595937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mashiach |
E146997
|
entity |
| Predicate | isExpectedTo |
P32577
|
FINISHED |
| Object | bring redemption to Israel |
—
|
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: bring redemption to Israel | Statement: [Mashiach, isExpectedTo, bring redemption to Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExpectedTo Context triple: [Mashiach, isExpectedTo, bring redemption to Israel]
-
A.
isSupposedToBe
chosen
Indicates that something is expected or intended to have a particular state, quality, or role, whether or not it actually does.
-
B.
anticipates
Indicates that one entity expects or predicts a future event, action, or state involving another entity before it actually occurs.
-
C.
endedFor
Indicates that a particular event, state, or process has come to an end for a specified entity or participant.
-
D.
predictedIn
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
-
E.
expectedBenefit
Indicates the benefit or positive outcome that is anticipated to result from a particular action, decision, or relationship between entities.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020bf77cc8190b8ca473c3a2e1d28 |
completed | March 22, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.