Triple
T31512982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gloria Burgle |
E803990
|
entity |
| Predicate | exSpouseTrait |
P91240
|
FINISHED |
| Object | comes out as gay during the series |
—
|
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: comes out as gay during the series | Statement: [Gloria Burgle, exSpouseTrait, comes out as gay during the series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exSpouseTrait Context triple: [Gloria Burgle, exSpouseTrait, comes out as gay during the series]
-
A.
spouseCharacteristic
chosen
Indicates that a particular characteristic, trait, or attribute is associated with a person’s spouse within the relationship.
-
B.
exSpouse
Indicates that two people were formerly married to each other but are no longer spouses.
-
C.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
D.
spouseCharacterOf
Indicates a marital relationship where one character is the spouse of another character.
-
E.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a21e3aa48190858d8afef5f759ef |
completed | May 3, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:51 p.m.