Triple
T15804503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korban Musaf |
E383175
|
entity |
| Predicate | categoryInHalakha |
P17761
|
FINISHED |
| Object | korbanot tzibbur |
—
|
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: korbanot tzibbur | Statement: [Korban Musaf, categoryInHalakha, korbanot tzibbur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categoryInHalakha Context triple: [Korban Musaf, categoryInHalakha, korbanot tzibbur]
-
A.
categoryInJudaism
Indicates that something belongs to, is classified within, or is recognized as a specific category or type in the context of Judaism.
-
B.
halachicCategory
chosen
Indicates the classification of something according to Jewish legal (halachic) categories or rulings.
-
C.
halachicSection
Indicates a relationship where a subject is classified under, or associated with, a specific section or subdivision within halachic (Jewish legal) texts or rulings.
-
D.
roleInHalacha
Indicates the specific function, status, or authority an entity holds within the framework of Jewish law (halacha).
-
E.
halachicNote
Indicates a relationship where one entity serves as a halachic (Jewish legal) note, comment, or annotation providing legal clarification or guidance about another entity.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b525b1c08190acffab06d89dbdbe |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.