Triple
T5260875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiur Komah |
E118819
|
entity |
| Predicate | hasPlaceInCanon |
P62601
|
FINISHED |
| Object | non-legal rabbinic literature |
—
|
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: non-legal rabbinic literature | Statement: [Shiur Komah, hasPlaceInCanon, non-legal rabbinic literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaceInCanon Context triple: [Shiur Komah, hasPlaceInCanon, non-legal rabbinic literature]
-
A.
hasPlaceInCanonLaw
Indicates that something holds a recognized status, role, or position within the system of canon law.
-
B.
notInCanonOf
Indicates that something is excluded from, or does not belong to, the officially recognized canon of a given work or universe.
-
C.
followsInCanon
Indicates that one entity occurs later than and in continuity with another within an established narrative or canonical sequence.
-
D.
canonizedIn
Indicates that an authority formally declared someone to be a saint or holy figure in a specified place or institution.
-
E.
hasFullNameInCanon
Indicates that an entity’s complete, official name is explicitly established within the canonical source material.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcf026c8190881b6e14b962a3c9 |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7bcabe58819096255672664513b1 |
completed | March 20, 2026, 4:54 p.m. |
Created at: March 20, 2026, 1:50 p.m.