Triple
T30933248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roy Anderson |
E788050
|
entity |
| Predicate | formerFiancéOf |
P71013
|
FINISHED |
| Object | Pam Beesly |
—
|
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: Pam Beesly | Statement: [Roy Anderson, formerFiancéOf, Pam Beesly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerFiancéOf Context triple: [Roy Anderson, formerFiancéOf, Pam Beesly]
-
A.
formerFiancéeOf
chosen
Indicates that one person was previously engaged to be married to another person, but the engagement has since ended.
-
B.
formerHusbandOf
Indicates that one person was previously the husband of another person, but the marital relationship has since ended.
-
C.
isFianceeOf
Indicates that one person is the engaged-to-be-married partner of another person.
-
D.
spouseOfFormer
Indicates that one entity is the spouse of another entity who is a former holder of some role, status, or position.
-
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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: April 29, 2026, 8:52 p.m.