Triple
T31701449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beatrice Lascelles |
E809065
|
entity |
| Predicate | spouseOfNotablePosition |
P87045
|
FINISHED |
| Object | 19th-century Archbishop of Canterbury |
—
|
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: 19th-century Archbishop of Canterbury | Statement: [Beatrice Lascelles, spouseOfNotablePosition, 19th-century Archbishop of Canterbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfNotablePosition Context triple: [Beatrice Lascelles, spouseOfNotablePosition, 19th-century Archbishop of Canterbury]
-
A.
spouseOffice
Indicates that one entity holds an office or position that is associated with, or held by, the spouse of another entity.
-
B.
spouseDiplomaticRole
Indicates that one person is the spouse of another person who holds or held a diplomatic position or role.
-
C.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
D.
spouseOfLeader
chosen
Indicates that one entity is the married partner (spouse) of another entity who holds a leadership position.
-
E.
spouseOfHeadOfState
Indicates that one person is the spouse (married partner) of a head of state.
- 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_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 30, 2026, 11:12 p.m.