Triple
T31248438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ספר בראשית |
E796750
|
entity |
| Predicate | מסורת ייחוס |
P111245
|
FINISHED |
| Object | מיוחס במסורת היהודית למשה רבנו |
—
|
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: מיוחס במסורת היהודית למשה רבנו | Statement: [ספר בראשית, מסורת ייחוס, מיוחס במסורת היהודית למשה רבנו]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: מסורת ייחוס Context triple: [ספר בראשית, מסורת ייחוס, מיוחס במסורת היהודית למשה רבנו]
-
A.
מסורת דתית
Indicates a relationship where an entity is associated with, follows, or is characterized by a particular religious tradition.
-
B.
מסורת מדרשית
Indicates a relationship where one entity is part of, derived from, or characterized by a specific midrashic (rabbinic interpretive) tradition.
-
C.
ייחוס
chosen
Indicates an attribution or assignment relationship, where a property, role, or characteristic is ascribed from one entity to another.
-
D.
traditionalJewishOrder
Indicates that something follows or conforms to the customary or historically established order used in Jewish tradition.
-
E.
eraWithinJudaism
Indicates that a time period or era occurs within, or is defined as part of, the broader historical or religious framework of Judaism.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:11 p.m.