Triple
T35985830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riki Johnson |
E1040704
|
entity |
| Predicate | saidToBeTheFirstHusbandOf |
P81982
|
FINISHED |
| Object | Charlotte Flair |
—
|
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: Charlotte Flair | Statement: [Riki Johnson, saidToBeTheFirstHusbandOf, Charlotte Flair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saidToBeTheFirstHusbandOf Context triple: [Riki Johnson, saidToBeTheFirstHusbandOf, Charlotte Flair]
-
A.
firstWifeOf
Indicates that one person is the first woman to have been married to another person.
-
B.
formerHusbandOf
Indicates that one person was previously the husband of another person, but the marital relationship has since ended.
-
C.
firstHusbandFatherOf
Indicates that the father of a person’s first husband is related to that person in the specified way.
-
D.
firstHusbandInstanceOf
chosen
Indicates that the entity is the first husband of another entity, specifying the initial marital partner in a sequence of spouses.
-
E.
allegedSpouseOf
Indicates a relationship where one person is claimed or reported to be the spouse of another, but the marital status is not legally or definitively confirmed.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.