Triple
T2515313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moshe Isserles |
E55398
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | HaMapah |
E55974
|
NE 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: HaMapah | Statement: [Moshe Isserles, notableWork, HaMapah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HaMapah Context triple: [Moshe Isserles, notableWork, HaMapah]
-
A.
Mapah
chosen
Mapah is Rabbi Moses Isserles’s glosses on the Shulchan Aruch, integrating Ashkenazi customs and rulings into that foundational Jewish legal code.
-
B.
Wallmapu
Wallmapu is the ancestral homeland of the Mapuche people, encompassing their traditional territories across parts of present-day Chile and Argentina.
-
C.
Ur Kasdim
Ur Kasdim is the ancient Mesopotamian city traditionally identified in the Hebrew Bible as the birthplace of the patriarch Abraham.
-
D.
Haran
Haran is an ancient city in northern Mesopotamia known from the Hebrew Bible as a key dwelling place of the patriarch Abraham before his journey to Canaan.
-
E.
HaRosh
HaRosh, also known as the Rosh, was a prominent medieval rabbi and halachic authority whose legal rulings significantly shaped later Jewish law.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd20db7e0819096d901eb20ae65e5 |
completed | March 7, 2026, 7:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af2b975e6881909b70a1795e8e2776 |
completed | March 9, 2026, 8:20 p.m. |
Created at: March 6, 2026, 9:46 p.m.