Triple
T32513576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krustofsky |
E830999
|
entity |
| Predicate | associatedWithFamilyMember |
P7844
|
FINISHED |
| Object | Rabbi Hyman Krustofsky |
E832619
|
NE 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: Rabbi Hyman Krustofsky | Statement: [Krustofsky, associatedWithFamilyMember, Rabbi Hyman Krustofsky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFamilyMember Context triple: [Krustofsky, associatedWithFamilyMember, Rabbi Hyman Krustofsky]
-
A.
familyAssociationWith
Indicates a familial relationship or connection exists between the referenced entities.
-
B.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
C.
hasFamilialTieTo
chosen
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
D.
coveredFamilyMember
Indicates that one person is included as an eligible dependent or beneficiary under another person’s insurance or benefit coverage.
-
E.
closelyLinkedToFamily
Indicates a strong, intimate, and ongoing connection or bond between an entity and its family.
- F. None of above.
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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a347b7aec8c8190858783e04869de5f |
completed | June 18, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1 a.m.