Triple
T10166081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ביכורים |
E235206
|
entity |
| Predicate | טעונים |
P92177
|
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.
arguesThat
Indicates that one entity presents reasons or justification in support of a specific claim, position, or proposition held about another entity or topic.
-
B.
claimsToExplain
Indicates that one entity asserts it can provide a clarification, account, or understanding of another entity or phenomenon.
-
C.
stanceOnProofs
Indicates the position or attitude an entity holds regarding the use, value, or nature of proofs.
-
D.
conditions
Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
-
E.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
- F. None of above. chosen
Provenance (4 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6cf27481909f38839452ac0e37 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:10 p.m.