Triple
T36395985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tractate Chagigah |
E896479
|
entity |
| Predicate | discussesCommandment |
P185734
|
FINISHED |
| Object | appearance in the Temple on festivals |
—
|
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: appearance in the Temple on festivals | Statement: [Tractate Chagigah, discussesCommandment, appearance in the Temple on festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discussesCommandment Context triple: [Tractate Chagigah, discussesCommandment, appearance in the Temple on festivals]
-
A.
containsCommandment
Indicates that one entity includes or encompasses a specific commandment as part of its content or structure.
-
B.
commandmentType
Indicates the specific category or kind of commandment that an instruction or directive belongs to.
-
C.
receivedCommandment
Indicates that one entity has been given or entrusted with a commandment, directive, or moral instruction from another entity.
-
D.
numberOfCommandments
Indicates the total count of commandments associated with a given subject.
-
E.
commandmentSource
Indicates that one entity is the origin, authority, or issuing source from which a particular commandment or directive is derived.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:10 p.m.