Triple
T34424117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Seeds |
E883623
|
entity |
| Predicate | hasKeyTractateForBlessings |
P37921
|
FINISHED |
| Object | Berakhot |
—
|
NE NERFINISHED |
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: Berakhot | Statement: [Order of Seeds, hasKeyTractateForBlessings, Berakhot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyTractateForBlessings Context triple: [Order of Seeds, hasKeyTractateForBlessings, Berakhot]
-
A.
containsTractate
chosen
Indicates that one entity includes or encompasses a specific tractate as part of its contents or structure.
-
B.
hasKeyRitual
Indicates that an entity is associated with or performs a primary or central ritual that is fundamental to its role, function, or identity.
-
C.
blessedWith
Indicates that one entity has received a positive gift, talent, quality, or advantage attributed to another source.
-
D.
associatedWithBlessing
Indicates a relationship in which an entity is connected to, linked with, or characterized by a blessing or act of blessing.
-
E.
blessedBy
Indicates that one entity has conferred a blessing, favor, or sacred endorsement upon 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 1, 2026, 2 a.m.