Triple
T34424271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nedarim |
E883626
|
entity |
| Predicate | traditionallyPrintedIn |
P93983
|
FINISHED |
| Object | standard Vilna edition of the Talmud |
—
|
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: standard Vilna edition of the Talmud | Statement: [Nedarim, traditionallyPrintedIn, standard Vilna edition of the Talmud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyPrintedIn Context triple: [Nedarim, traditionallyPrintedIn, standard Vilna edition of the Talmud]
-
A.
printedEditions
Indicates that one entity has produced or issued physical printed versions (editions) of another entity.
-
B.
printedEdition
chosen
Indicates that one entity is a printed (physical) edition or version of another entity.
-
C.
hasBeenReprintedIn
Indicates that an item (such as a work or edition) has been published again in another source, format, or collection.
-
D.
printedFirstEditionOf
Indicates that the subject entity produced and issued the initial published edition of the object entity.
-
E.
printsPublishedIn
Indicates that a print (such as an artwork or printed item) was published in a specific publication, venue, or medium.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: May 1, 2026, 2 a.m.