Triple
T15886410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | get (Jewish bill of divorce) |
E385202
|
entity |
| Predicate | mustBeGrantedBy |
P2246
|
FINISHED |
| Object | husband |
—
|
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: husband | Statement: [get (Jewish bill of divorce), mustBeGrantedBy, husband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustBeGrantedBy Context triple: [get (Jewish bill of divorce), mustBeGrantedBy, husband]
-
A.
mustGrant
Indicates that one party is obligated to give or allow something (such as a right, permission, or resource) to another party.
-
B.
grantedBy
chosen
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
C.
grantedWith
Indicates that one entity is given, conferred, or endowed together with another entity as part of the same granting event or condition.
-
D.
isGrantedFor
Indicates that a permission, right, or benefit has been formally given to a specific entity for a particular purpose or use.
-
E.
believedToGrant
Indicates that something is thought or assumed to provide, confer, or bestow a particular benefit, quality, or effect.
- 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.