Triple
T34666805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | מסכת מועד קטן |
E890278
|
entity |
| Predicate | isCanonicalIn |
P128604
|
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: [מסכת מועד קטן, isCanonicalIn, המסורת הרבנית]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCanonicalIn Context triple: [מסכת מועד קטן, isCanonicalIn, המסורת הרבנית]
-
A.
isCanonical
Indicates that something represents the standard, authoritative, or officially accepted form within a given context or system.
-
B.
isCanonicalOn
Indicates that something is recognized as the standard or authoritative form of another entity within a given context.
-
C.
isCanonicalWithRespectTo
Indicates that something conforms to, or is expressed in, a standard or authoritative form relative to a specified framework, reference, or set of rules.
-
D.
isCanonicalFormOf
Indicates that one entity is the standard or officially accepted form or representation of another, often more variant, entity.
-
E.
isCanonicalWorkIn
chosen
Indicates that a work is recognized as an official or authoritative entry within a specified collection, corpus, or canon.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722f81fc48190bed78b48e86e15e2 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.