Triple
T31701448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beatrice Lascelles |
E809065
|
entity |
| Predicate | spouseOfReligiousDenomination |
P137514
|
FINISHED |
| Object | Anglican |
—
|
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: Anglican | Statement: [Beatrice Lascelles, spouseOfReligiousDenomination, Anglican]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfReligiousDenomination Context triple: [Beatrice Lascelles, spouseOfReligiousDenomination, Anglican]
-
A.
spouseReligiousRole
Indicates that one person’s role or position in a religious context is defined in relation to their spouse’s religious role.
-
B.
spouseOfReligiousMovement
Indicates a marital relationship where one spouse is associated with, belongs to, or is significantly involved in a particular religious movement.
-
C.
spouseReligiousTradition
chosen
Indicates that there is a relationship specifying the religious tradition or affiliation of a person's spouse.
-
D.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
-
E.
spouseTempleName
Indicates that one person is the spouse of another person identified specifically by their temple name.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 30, 2026, 11:12 p.m.