Triple
T15886863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebbetzin |
E385212
|
entity |
| Predicate | relationshipToRabbi |
P94755
|
FINISHED |
| Object | spouse |
—
|
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: spouse | Statement: [Rebbetzin, relationshipToRabbi, spouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToRabbi Context triple: [Rebbetzin, relationshipToRabbi, spouse]
-
A.
relationshipToJews
Indicates how an entity is related or connected to Jewish people, communities, or Judaism.
-
B.
relationshipToRelative
chosen
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
C.
relationshipToReligion
Indicates the nature or type of connection an entity has to a religion, such as affiliation, stance, or involvement.
-
D.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
E.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
- 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.