Triple
T37584152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegula family |
E935052
|
entity |
| Predicate | primaryPatriarch |
P9498
|
FINISHED |
| Object | Terry Pegula |
E53778
|
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: Terry Pegula | Statement: [Pegula family, primaryPatriarch, Terry Pegula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPatriarch Context triple: [Pegula family, primaryPatriarch, Terry Pegula]
-
A.
patriarch
chosen
Indicates a relationship where one entity serves as the male head or senior father-figure authority over a family, clan, or lineage of other entities.
-
B.
primaryHeir
Indicates that one entity is the main or principal inheritor of another entity’s estate, title, or rights.
-
C.
patriarchRank
Indicates the hierarchical rank or level of authority held by a patriarch within a structured lineage or leadership system.
-
D.
primaryFamily
Indicates that one entity is the main or principal family unit to which another entity is most closely or formally associated.
-
E.
patriarchFeatured
Indicates that a patriarch is prominently highlighted or given special emphasis in relation to something (such as a work, event, or context).
- 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_6a40ba419c688190956ed23a437e8015 |
completed | June 28, 2026, 6: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.