Triple
T31248725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | לבן הארמי |
E796756
|
entity |
| Predicate | ניסה_לשנות |
P120620
|
FINISHED |
| Object | שכרו_של_יעקב |
—
|
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: שכרו_של_יעקב | Statement: [לבן הארמי, ניסה_לשנות, שכרו_של_יעקב]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ניסה_לשנות Context triple: [לבן הארמי, ניסה_לשנות, שכרו_של_יעקב]
-
A.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
B.
canChangeIn
Indicates that one entity is capable of undergoing alteration, transformation, or variation within the context or influence of another entity or condition.
-
C.
changesMindAfter
chosen
Indicates that one entity revises or reverses a previously held decision, opinion, or intention after another entity’s action, statement, or influence.
-
D.
namespaceChangedTo
Indicates that an entity’s namespace has been updated or reassigned from its previous value to a new one.
-
E.
renews
Indicates that one entity extends, refreshes, or restores the validity, duration, or effectiveness of another entity, often continuing a prior agreement, state, or condition.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:11 p.m.