Triple
T35244328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | yeshivot of Central Europe |
E1017616
|
entity |
| Predicate | usedStudyMethod |
P40422
|
FINISHED |
| Object | pilpul |
—
|
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: pilpul | Statement: [yeshivot of Central Europe, usedStudyMethod, pilpul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedStudyMethod Context triple: [yeshivot of Central Europe, usedStudyMethod, pilpul]
-
A.
studyMethods
chosen
Indicates that an entity uses or engages in particular methods or techniques for studying.
-
B.
isStudiedUsing
Indicates that something serves as the method, tool, or approach by which something else is examined, analyzed, or researched.
-
C.
typicalStudyMode
Indicates the usual or most common way in which an entity conducts or experiences a study or learning activity.
-
D.
studiesFor
Indicates that one entity engages in studying or academic preparation with the purpose of achieving or supporting another entity (such as a goal, exam, or qualification).
-
E.
study
Indicates engaging in a systematic effort to learn, understand, or investigate a subject or object.
- 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.