Triple
T34630624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlanta Exes |
E889269
|
entity |
| Predicate | featuresExSpouseConnection |
—
|
GENERATED |
| Object | Usher |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresExSpouseConnection Context triple: [Atlanta Exes, featuresExSpouseConnection, Usher]
-
A.
hasMemberSpouseConnection
Indicates a relationship where one entity is a spouse of a member associated with the other entity.
-
B.
spouseCharacteristic
Indicates that a particular characteristic, trait, or attribute is associated with a person’s spouse within the relationship.
-
C.
spouseFatherMemberOf
Indicates that the father of a person’s spouse is a member of a specified group, organization, or entity.
-
D.
spouseMemberOf
Indicates that a person’s spouse is a member of a specified group, organization, or entity.
-
E.
spouseInFamily
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
- F. None of above. chosen
Provenance (1 batch)
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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:04 a.m.