Triple
T5565303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | אֵלִיָּהוּ |
E145865
|
entity |
| Predicate | תפקיד במסורת הנוצרית |
P27433
|
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.
ecclesiasticalRole
Indicates that one entity holds or is assigned a specific religious or church-related office, function, or position in relation to another entity.
-
B.
biblicalFigureRole
chosen
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative or tradition.
-
C.
eraOfReligiousFunction
Indicates the historical time period during which a religious role, office, or function was actively performed or held.
-
D.
liturgicalRole
Indicates the specific function or position an entity holds within a religious or liturgical context.
-
E.
religiousTextRole
Indicates the specific role or function that a religious text has in relation to a person, group, practice, or tradition.
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02033cc308190895f13454c57f452 |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b12826c8190969a584d0f53aa44 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.