Triple
T21148129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beelzebub |
E521113
|
entity |
| Predicate | viewInRabbinicLiterature |
P18949
|
FINISHED |
| Object | major demon |
—
|
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: major demon | Statement: [Beelzebub, viewInRabbinicLiterature, major demon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewInRabbinicLiterature Context triple: [Beelzebub, viewInRabbinicLiterature, major demon]
-
A.
rabbinicSource
Indicates that one entity serves as a rabbinic or Talmudic source or authority for the other.
-
B.
themeInRabbinicLiterature
chosen
Indicates that a particular theme, concept, or motif is discussed, developed, or treated within rabbinic literature.
-
C.
appearsInTractate
Indicates that one entity (such as a topic, law, or passage) is contained within or discussed in a particular tractate.
-
D.
halakhicSource
Indicates a relationship where one item serves as the halakhic (Jewish legal) basis, authority, or source text for another.
-
E.
viewsHalakhaAs
Indicates that one entity regards or interprets Halakha (Jewish law) in a particular way, such as considering it authoritative, binding, flexible, or symbolic.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723fe9da88190b65c370b1efcbb96 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.