Triple
T21911497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kay Guarrera |
E541073
|
entity |
| Predicate | spouseNotableTitle |
P17687
|
FINISHED |
| Object | undisputed middleweight boxing champion |
—
|
LITERAL FINISHED |
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: undisputed middleweight boxing champion | Statement: [Kay Guarrera, spouseNotableTitle, undisputed middleweight boxing champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseNotableTitle Context triple: [Kay Guarrera, spouseNotableTitle, undisputed middleweight boxing champion]
-
A.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
B.
spouseNotableAward
Indicates that a person’s spouse has received a notable award or honor.
-
C.
hasSpouseTitle
chosen
Indicates that a person’s spouse holds a particular title or honorific designation.
-
D.
spouseNotableWorkField
Indicates that the notable work or professional field associated with a person’s spouse is being specified.
-
E.
isSpouseOfTitle
Indicates that one entity holds a spousal relationship specifically associated with a titled or honorific status of another entity.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f121da36e88190b42b82641ec54a19 |
completed | April 28, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:41 p.m.