Triple
T5182217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commentary on the Talmud |
E116946
|
entity |
| Predicate | authorReligiousRole |
P51786
|
FINISHED |
| Object | rabbi |
—
|
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: rabbi | Statement: [Commentary on the Talmud, authorReligiousRole, rabbi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorReligiousRole Context triple: [Commentary on the Talmud, authorReligiousRole, rabbi]
-
A.
religiousTextRole
Indicates the specific role or function that a religious text has in relation to a person, group, practice, or tradition.
-
B.
religiousFigure
Indicates that one entity is recognized or designated as a religious leader, authority, or sacred person in relation to another entity.
-
C.
eraOfReligiousFunction
Indicates the historical time period during which a religious role, office, or function was actively performed or held.
-
D.
theologicalRole
Indicates a relationship where an entity holds or is assigned a specific function, office, or status within a theological or religious framework.
-
E.
associatedReligionRole
chosen
Indicates that one entity holds a specific religious role, office, or function in relation to 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd799d50388190bf2b7dfdd90949e9 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.