Triple
T696736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish Temple |
E13909
|
entity |
| Predicate | ritualLaw |
P4193
|
FINISHED |
| Object | Torah commandments |
—
|
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: Torah commandments | Statement: [Jewish Temple, ritualLaw, Torah commandments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualLaw Context triple: [Jewish Temple, ritualLaw, Torah commandments]
-
A.
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.
-
B.
hasRitual
chosen
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
C.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
D.
customaryLaw
Indicates that a relationship, behavior, or rule is governed by unwritten, traditional norms and practices recognized as binding within a community or group.
-
E.
hasLifecycleRitual
Indicates that an entity is associated with a ritual or ceremonial practice marking a significant stage or transition in its lifecycle.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c8055881909565ebde2be8fd7a |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d2586b081908e052cc5ba1d2685 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.