Triple
T4652390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takanot |
E102324
|
entity |
| Predicate | mayModify |
P48269
|
FINISHED |
| Object | application of biblical 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: application of biblical law | Statement: [Takanot, mayModify, application of biblical law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayModify Context triple: [Takanot, mayModify, application of biblical law]
-
A.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
-
B.
mayAmend
chosen
Indicates that one party has the authority or permission to modify, revise, or change something that already exists.
-
C.
mayRemove
Indicates that one entity is permitted or authorized to remove another entity or its association.
-
D.
maySign
Indicates that an entity has the permission or authority to sign a document, agreement, or similar item.
-
E.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
- 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6314883481908f085a7af497b0d8 |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.