Triple
T25060907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinhas |
E627653
|
entity |
| Predicate | associatedWithParashah |
P178742
|
FINISHED |
| Object | Parashat Pinchas |
—
|
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: Parashat Pinchas | Statement: [Pinhas, associatedWithParashah, Parashat Pinchas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithParashah Context triple: [Pinhas, associatedWithParashah, Parashat Pinchas]
-
A.
containsParshiyot
Indicates that one textual or structural unit (such as a Torah scroll or section) includes within it one or more parshiyot (distinct Torah portions or sections).
-
B.
associatedWithVerse
Indicates a relationship where something is linked or connected to a specific verse, typically in a text or scripture.
-
C.
subsectionOfTanakh
Indicates that one text division is a recognized subsection within the larger structure of the Tanakh.
-
D.
associatedWithBiblicalChapter
Indicates that something has a specified connection or linkage to a particular chapter in the Bible.
-
E.
appearsInTractate
Indicates that one entity (such as a topic, law, or passage) is contained within or discussed in a particular tractate.
- F. None of above. chosen
Provenance (4 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 18, 2026, 6:10 a.m.