Triple
T5243068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabbi Nehunia ben HaKana |
E118390
|
entity |
| Predicate | prayerAttributed |
P21327
|
FINISHED |
| Object | prayer when entering the beit midrash |
—
|
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: prayer when entering the beit midrash | Statement: [Rabbi Nehunia ben HaKana, prayerAttributed, prayer when entering the beit midrash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prayerAttributed Context triple: [Rabbi Nehunia ben HaKana, prayerAttributed, prayer when entering the beit midrash]
-
A.
associatedPrayer
chosen
Indicates a relationship where a specific prayer is linked or connected to another entity, such as an event, object, person, or religious context.
-
B.
praysAt
Indicates that one entity performs an act of prayer at, or directed toward, a specific place or site.
-
C.
isAddressedInPrayer
Indicates that an entity is the recipient or target of a prayer being spoken or offered.
-
D.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
-
E.
prayerCall
Indicates that one entity issues or performs a call to prayer directed toward others.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b4da7308190856cdcee9cca41eb |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.