Triple
T5533115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sefer HaMadda |
E145095
|
entity |
| Predicate | componentOfSystem |
P840
|
FINISHED |
| Object | comprehensive code of Jewish law |
—
|
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: comprehensive code of Jewish law | Statement: [Sefer HaMadda, componentOfSystem, comprehensive code of Jewish law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentOfSystem Context triple: [Sefer HaMadda, componentOfSystem, comprehensive code of Jewish law]
-
A.
partOfSystem
chosen
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
-
B.
isCoreComponentOf
Indicates that something is an essential, foundational part required for the structure, function, or identity of another entity.
-
C.
component1
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
D.
component3
Indicates that one entity is the third component or sub-part within a larger composite structure or system involving another entity.
-
E.
componentFrom
Indicates that one entity is derived from, produced by, or originates as a component of another entity.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f9ea2c88190a68642f5799bd8ff |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.