Triple
T4664116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sifre Zuta |
E102803
|
entity |
| Predicate | commentaryType |
P45476
|
FINISHED |
| Object | midrashic commentary |
—
|
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: midrashic commentary | Statement: [Sifre Zuta, commentaryType, midrashic commentary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commentaryType Context triple: [Sifre Zuta, commentaryType, midrashic commentary]
-
A.
commentaryOn
Indicates that one entity provides evaluative or explanatory remarks about another entity, such as a work, event, or statement.
-
B.
typeOfCommentary
chosen
Indicates that one piece of commentary is a specific kind or subtype of another, more general category of commentary.
-
C.
commentaryFocus
Indicates that an item of commentary is primarily directed toward or centered on a particular entity, topic, or aspect.
-
D.
metaCommentaryOn
Indicates that one piece of content provides commentary, reflection, or analysis about another piece of content, often discussing its form, structure, or status as a work rather than its subject matter.
-
E.
hasCommentaryOn
Indicates that one entity provides commentary, explanation, or evaluative remarks about 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd633aeba88190a8329ed022d685b6 |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.