Triple
T13040810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabbi Akiva Eiger |
E327184
|
entity |
| Predicate | rabbinicStatus |
P75458
|
FINISHED |
| Object | gaon |
—
|
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: gaon | Statement: [Rabbi Akiva Eiger, rabbinicStatus, gaon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rabbinicStatus Context triple: [Rabbi Akiva Eiger, rabbinicStatus, gaon]
-
A.
halakhicStatus
Indicates the formal standing or classification of an entity according to Jewish law (halakha), especially in terms of what is religiously permitted, required, or prohibited.
-
B.
rabbinicSource
Indicates that one entity serves as a rabbinic or Talmudic source or authority for the other.
-
C.
orthodoxStatus
Indicates that an entity conforms to, aligns with, or is recognized as following an established or traditional set of doctrines, beliefs, or practices.
-
D.
halachicSection
Indicates a relationship where a subject is classified under, or associated with, a specific section or subdivision within halachic (Jewish legal) texts or rulings.
-
E.
roleInHalacha
chosen
Indicates the specific function, status, or authority an entity holds within the framework of Jewish law (halacha).
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:56 p.m.