Triple
T26346741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonya Szatkowski |
E662794
|
entity |
| Predicate | spouseRingName |
P155170
|
FINISHED |
| Object | Rob Van Dam |
—
|
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: Rob Van Dam | Statement: [Sonya Szatkowski, spouseRingName, Rob Van Dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseRingName Context triple: [Sonya Szatkowski, spouseRingName, Rob Van Dam]
-
A.
spouseRingNameOf
chosen
Indicates that the object is the name inscribed on, or associated with, the spouse’s ring belonging to the subject.
-
B.
spouse name
Indicates that one entity is the legally recognized husband or wife of the other, specifying the partner’s name in a marital relationship.
-
C.
spouseGivenName
Indicates that the value is the given (first) name of a person's spouse in the relationship.
-
D.
namedForSpouse
Indicates that one entity is named after the spouse of another entity.
-
E.
spouseRealName
Indicates that one person is the legally recognized spouse of another, using the spouse’s real (non-alias) name.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 26, 2026, 10:42 p.m.