Triple
T6673522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishneh LaMelech |
E151791
|
entity |
| Predicate | religiousLawField |
P17762
|
FINISHED |
| Object | civil law in Halakha |
—
|
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: civil law in Halakha | Statement: [Mishneh LaMelech, religiousLawField, civil law in Halakha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousLawField Context triple: [Mishneh LaMelech, religiousLawField, civil law in Halakha]
-
A.
religiousJurisdiction
Indicates that one entity holds official religious authority or governance over another entity or area.
-
B.
religiousCanon
Indicates that something is formally recognized as part of an established body of authoritative religious texts or doctrine.
-
C.
scripturalLawCode
Indicates that one entity is a law code or set of legal prescriptions as defined or authorized by a particular scriptural or religious text for another entity.
-
D.
religiousScholarship
Indicates a relationship where an entity provides or is associated with financial or institutional support specifically for religious study or education.
-
E.
halakhicSource
chosen
Indicates a relationship where one item serves as the halakhic (Jewish legal) basis, authority, or source text for another.
- 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_69c687f830bc81909eb8b04dbb8450b1 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:03 p.m.