Triple
T15802060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | yeshivot of Mainz |
E383120
|
entity |
| Predicate | scholarlyOutput |
P34352
|
FINISHED |
| Object | halakhic rulings |
—
|
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: halakhic rulings | Statement: [yeshivot of Mainz, scholarlyOutput, halakhic rulings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scholarlyOutput Context triple: [yeshivot of Mainz, scholarlyOutput, halakhic rulings]
-
A.
scholarlyWork
Indicates a relationship where an entity is a formal academic or research work produced, published, or recognized within a scholarly context.
-
B.
scholarlyActivity
Indicates engagement in academic or research-related work, such as studying, teaching, publishing, or conducting scholarly inquiry.
-
C.
scholarlyMilieu
Indicates the intellectual or academic environment, context, or community within which a scholarly work, activity, or figure is situated.
-
D.
hasResearchOutput
chosen
Indicates that an entity produces, is associated with, or is responsible for a particular research output or scholarly work.
-
E.
scholarlyUse
Indicates that something is used for academic, educational, or research-related purposes.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b523bf508190af4a54bdc983a9a1 |
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.