Triple
T10166170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terumah |
E235208
|
entity |
| Predicate | statusOutsideTemple |
P92181
|
FINISHED |
| Object | continues to apply in rabbinic law |
—
|
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: continues to apply in rabbinic law | Statement: [Terumah, statusOutsideTemple, continues to apply in rabbinic law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOutsideTemple Context triple: [Terumah, statusOutsideTemple, continues to apply in rabbinic law]
-
A.
positionInTemple
Indicates the specific location or role an entity occupies within a temple.
-
B.
statusInTemplePeriod
Indicates the role, condition, or standing that an entity held during the specified temple period.
-
C.
roleAtTemple
Indicates that an entity holds or performs a specific role, function, or position at a particular temple.
-
D.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
E.
hasTempleLocation
Indicates that a temple is located at or associated with a specific place or geographic location.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6cf27481909f38839452ac0e37 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:10 p.m.