Triple
T11560907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rema |
E274139
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | HaMapah |
E276449
|
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: [Rema, notableWork, HaMapah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HaMapah Context triple: [Rema, notableWork, HaMapah]
-
A.
Mappah
chosen
Mappah is a halachic work by Rabbi Moshe Isserles that supplements and adapts the Shulchan Aruch to Ashkenazi Jewish legal customs.
-
B.
Hamap
Hamap is a Papuan language spoken on the Alor–Pantar archipelago in eastern Indonesia.
-
C.
Ha’apalah
Ha’apalah was the clandestine immigration movement that brought Jewish refugees to Mandatory Palestine in defiance of British restrictions before the establishment of the State of Israel.
-
D.
Hapur
Hapur is a city in the Indian state of Uttar Pradesh, known as an industrial and grain market hub within the Delhi metropolitan area.
-
E.
Eshtaol
Eshtaol is an ancient town in the Shephelah region of Judah, mentioned in the Hebrew Bible as a key settlement associated with the Tribe of Dan.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a899d4481909a3bce3147763b51 |
completed | April 10, 2026, 5:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6e88b84d48190948243646bb5fd2b |
completed | April 21, 2026, 3:01 a.m. |
Created at: April 8, 2026, 9:37 p.m.