Triple
T34689928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridey Murphy |
E890862
|
entity |
| Predicate | allegedHusbandName |
P187080
|
FINISHED |
| Object | Sean Brian McCarthy |
—
|
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: Sean Brian McCarthy | Statement: [Bridey Murphy, allegedHusbandName, Sean Brian McCarthy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedHusbandName Context triple: [Bridey Murphy, allegedHusbandName, Sean Brian McCarthy]
-
A.
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.
-
B.
formerHusbandOf
Indicates that one person was previously the husband of another person, but the marital relationship has since ended.
-
C.
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.
-
D.
spouseGivenName
Indicates that the value is the given (first) name of a person's spouse in the relationship.
-
E.
spouseRealName
Indicates that one person is the legally recognized spouse of another, using the spouse’s real (non-alias) name.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: May 1, 2026, 2:05 a.m.