Triple
T12666524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aruch HaShulchan |
E302565
|
entity |
| Predicate | approachToRuling |
P42260
|
FINISHED |
| Object | tends toward practical consensus |
—
|
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: tends toward practical consensus | Statement: [Aruch HaShulchan, approachToRuling, tends toward practical consensus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachToRuling Context triple: [Aruch HaShulchan, approachToRuling, tends toward practical consensus]
-
A.
laysDownRulingOn
Indicates that an authority formally issues or establishes a decision, judgment, or rule concerning a particular matter or case.
-
B.
constitutionalRuling
Indicates a formal judicial decision determining whether a law, policy, or government action complies with a constitution.
-
C.
legalRulingNature
chosen
Indicates the type or character of a legal ruling, such as its form, basis, or procedural nature.
-
D.
decisionMakingRule
Indicates the principle, guideline, or procedure that governs how a decision is made in a given context.
-
E.
ratioDecidendi
Indicates the legal reasoning or principle that forms the binding basis for a court’s decision in a case.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96181c40481908f3e2717f5472b85 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:19 p.m.