Triple
T36078716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darren Silverman |
E1043571
|
entity |
| Predicate | finalPartner |
P123045
|
FINISHED |
| Object | Sandy Perkus |
—
|
NE NERFINISHED |
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: Sandy Perkus | Statement: [Darren Silverman, finalPartner, Sandy Perkus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalPartner Context triple: [Darren Silverman, finalPartner, Sandy Perkus]
-
A.
finalSpouse
chosen
Indicates that one person is the last spouse of another person, with no subsequent spouses after this relationship.
-
B.
partnerInEndingWith
Indicates that an entity participates as a partner in an event, process, or relationship that concludes with a specified outcome or terminal state.
-
C.
parter
Indicates that two entities are partners, typically engaged in a shared, cooperative, or jointly responsible relationship.
-
D.
formerPartner
Indicates that one entity was previously in a romantic or partnership relationship with another entity, but that relationship has since ended.
-
E.
partnerInFinalReconciliation
Indicates that two or more entities jointly participate as partners in a final act or process of reconciliation.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 3, 2026, 4:08 p.m.