Triple
T37584153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegula family |
E935052
|
entity |
| Predicate | primaryMatriarch |
P9499
|
FINISHED |
| Object | Kim Pegula |
E53779
|
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: Kim Pegula | Statement: [Pegula family, primaryMatriarch, Kim Pegula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMatriarch Context triple: [Pegula family, primaryMatriarch, Kim Pegula]
-
A.
matriarch
chosen
Indicates that one entity holds the role or status of a female head or leading maternal figure in relation to another entity or group.
-
B.
primaryHeir
Indicates that one entity is the main or principal inheritor of another entity’s estate, title, or rights.
-
C.
ancestorMother
Indicates that one entity is a female ancestor (mother, grandmother, etc.) of another entity in a family lineage.
-
D.
motherRole
Indicates that one entity holds the role or function of a mother in relation to another entity.
-
E.
isMaternalFigureOf
Indicates a nurturing, protective, and guiding parental-like relationship that one individual has toward another, typically in a motherly role.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40d665f2b081909d01d83c055d4116 |
completed | June 28, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.