Triple
T15886449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | get (Jewish bill of divorce) |
E385202
|
entity |
| Predicate | mayBeReceivedBy |
P52361
|
FINISHED |
| Object | agent (shaliach) of the wife |
—
|
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: agent (shaliach) of the wife | Statement: [get (Jewish bill of divorce), mayBeReceivedBy, agent (shaliach) of the wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeReceivedBy Context triple: [get (Jewish bill of divorce), mayBeReceivedBy, agent (shaliach) of the wife]
-
A.
hasReceiver
Indicates that an entity serves as the recipient or target of something provided, sent, or directed by another entity.
-
B.
recipientOf
chosen
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
-
C.
hasRecipientRole
Indicates that a specified entity serves as the recipient or target role in a given interaction, transaction, or relationship.
-
D.
canBeReceivedOnce
Indicates that the referenced item, benefit, or action may only be obtained a single time by a given recipient.
-
E.
intendedReceiver
Indicates that one entity is the target or designated recipient of something (such as a message, item, or action) originating from another entity.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.