Triple
T34184657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israel Meir Lau |
E876924
|
entity |
| Predicate | rabbinicTradition |
P178496
|
FINISHED |
| Object | Haredi Judaism |
—
|
NE NERFINISHED |
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: Haredi Judaism | Statement: [Israel Meir Lau, rabbinicTradition, Haredi Judaism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rabbinicTradition Context triple: [Israel Meir Lau, rabbinicTradition, Haredi Judaism]
-
A.
rabbinicSource
Indicates that one entity serves as a rabbinic or Talmudic source or authority for the other.
-
B.
halakhicAuthorityTradition
Indicates that one entity serves as a recognized source or lineage of binding Jewish legal (halakhic) guidance and decision-making for another.
-
C.
eraWithinJudaism
Indicates that a time period or era occurs within, or is defined as part of, the broader historical or religious framework of Judaism.
-
D.
traditionalJewishOrder
Indicates that something follows or conforms to the customary or historically established order used in Jewish tradition.
-
E.
מסורת קבלית
Indicates a relationship in which knowledge, practices, or interpretations are transmitted and received through a Kabbalistic tradition.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710aaff588190adc6cc5b7d5424cc |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fddd43c819088dee5a448c72cbe |
completed | May 3, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:55 a.m.