Triple
T25768040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tur Even Ha’ezer |
E648935
|
entity |
| Predicate | authorOfParentWork |
P166593
|
FINISHED |
| Object | Rabbi Jacob ben Asher |
—
|
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: Rabbi Jacob ben Asher | Statement: [Tur Even Ha’ezer, authorOfParentWork, Rabbi Jacob ben Asher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorOfParentWork Context triple: [Tur Even Ha’ezer, authorOfParentWork, Rabbi Jacob ben Asher]
-
A.
authorOfWorkAppearingIn
Indicates that one entity is the creator or writer of a work that appears within another work or publication.
-
B.
authorOfPreviousWork
Indicates that one entity is the creator or writer of an earlier work referenced or built upon by another entity.
-
C.
authorOfCompanionWork
Indicates that one entity is the creator or writer of another entity that serves as a companion or supplementary work to a primary work.
-
D.
authorFather
Indicates that one entity is the father of another entity who is the author of a work.
-
E.
authorAsCredited
Indicates the relationship between a work and the person or entity credited as its author, regardless of actual authorship.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 22, 2026, 5:12 a.m.