Triple
T2113091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weeks |
E42546
|
entity |
| Predicate | biblicalCommandment |
P7169
|
FINISHED |
| Object | pilgrimage festival |
—
|
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: pilgrimage festival | Statement: [Weeks, biblicalCommandment, pilgrimage festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalCommandment Context triple: [Weeks, biblicalCommandment, pilgrimage festival]
-
A.
commandmentType
chosen
Indicates the specific category or kind of commandment that an instruction or directive belongs to.
-
B.
numberOfCommandments
Indicates the total count of commandments associated with a given subject.
-
C.
commandmentHebrewName
Indicates the Hebrew-language name assigned to a particular commandment.
-
D.
scripturalLawCode
Indicates that one entity is a law code or set of legal prescriptions as defined or authorized by a particular scriptural or religious text for another entity.
-
E.
scripturalBasis
Indicates that one entity serves as the religious or scriptural foundation, support, or justification for another entity (such as a belief, practice, or doctrine).
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb0495d0819097dc936540743b74 |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.