Triple
T25651238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas (enslaved husband) |
E643103
|
entity |
| Predicate | spouseNameAtTheTime |
P165315
|
FINISHED |
| Object | Isabella (Sojourner Truth’s birth name) |
—
|
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: Isabella (Sojourner Truth’s birth name) | Statement: [Thomas (enslaved husband), spouseNameAtTheTime, Isabella (Sojourner Truth’s birth name)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseNameAtTheTime Context triple: [Thomas (enslaved husband), spouseNameAtTheTime, Isabella (Sojourner Truth’s birth name)]
-
A.
spouseNameAtMarriage
Indicates the full name a person’s spouse had at the time of their marriage.
-
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.
spouseBirthName
Indicates the birth name of a person's spouse, prior to any name changes such as through marriage.
-
D.
spouseAlsoKnownAs
Indicates that a person’s spouse is referred to by an alternative name or alias.
-
E.
namedForSpouse
Indicates that one entity is named after the spouse of another entity.
- F. None of above. chosen
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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 21, 2026, 6:23 p.m.