Triple
T22216044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shloshah Asar Ikkarim |
E549075
|
entity |
| Predicate | formulatedInSection |
P3660
|
FINISHED |
| Object | Introduction to Perek Chelek |
—
|
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: Introduction to Perek Chelek | Statement: [Shloshah Asar Ikkarim, formulatedInSection, Introduction to Perek Chelek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formulatedInSection Context triple: [Shloshah Asar Ikkarim, formulatedInSection, Introduction to Perek Chelek]
-
A.
operatorInSection
Indicates that an operator is assigned to, works within, or is responsible for a specific section.
-
B.
sectionProvided
Indicates that a specific section or portion of content has been supplied or made available by one entity to another.
-
C.
hasFormulation
chosen
Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
-
D.
section
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
E.
sectionIntroduced
Indicates that a particular section was introduced or added at a specific point in time or context.
- 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b8bdfbc8190832809edbe8b7c27 |
completed | April 28, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.