Triple
T24381438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilchot Nachalot |
E614621
|
entity |
| Predicate | followsLegalSource |
P65906
|
FINISHED |
| Object | Talmud |
—
|
NE NERFINISHED |
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: Talmud | Statement: [Hilchot Nachalot, followsLegalSource, Talmud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsLegalSource Context triple: [Hilchot Nachalot, followsLegalSource, Talmud]
-
A.
followsLegalAuthority
Indicates that one entity acts in accordance with, or is subordinate to, the legal power, rules, or jurisdiction exercised by another entity.
-
B.
majorLegalSource
chosen
Indicates that one entity serves as a primary or authoritative legal basis or reference for another entity.
-
C.
hasLegalSubject
Indicates that an entity serves as the legal subject (e.g., rights-holder or obligated party) in a legal relationship or context.
-
D.
hasLegalLink
Indicates a formal legal relationship or connection exists between the referenced entities, such as through contracts, regulations, or legal obligations.
-
E.
legislationSource
Indicates that one entity serves as the originating authority, basis, or source for a particular piece of legislation or legal rule.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293dc0c3c8190ad6de5db50ccbd76 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.