Triple
T31248741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | לבן הארמי |
E796756
|
entity |
| Predicate | מסורת_פרשנית |
P172860
|
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 one entity is part of, derived from, or characterized by a specific midrashic (rabbinic interpretive) tradition.
-
B.
מסורת קבלית
Indicates a relationship in which knowledge, practices, or interpretations are transmitted and received through a Kabbalistic tradition.
-
C.
מסורת דתית
Indicates a relationship where an entity is associated with, follows, or is characterized by a particular religious tradition.
-
D.
מסורת חז"ל
Indicates the relationship in which something is based on, derived from, or in accordance with the rabbinic tradition and teachings of the Sages (Chazal).
-
E.
מאפיין פרשנות
Indicates that something characterizes or defines a particular interpretation.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 29, 2026, 9:11 p.m.