Triple
T14205897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard of Conisburgh, 3rd Earl of Cambridge |
E352093
|
entity |
| Predicate | throughSpouse |
P113199
|
FINISHED |
| Object | Mortimer claim to the English throne |
—
|
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: Mortimer claim to the English throne | Statement: [Richard of Conisburgh, 3rd Earl of Cambridge, throughSpouse, Mortimer claim to the English throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: throughSpouse Context triple: [Richard of Conisburgh, 3rd Earl of Cambridge, throughSpouse, Mortimer claim to the English throne]
-
A.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
B.
metSpouseThrough
Indicates that one person became acquainted with and subsequently married their spouse as a result of a particular intermediary person, event, place, or context.
-
C.
granteeSpouse
Indicates that one person is the spouse of the person who receives a grant, transfer, or similar benefit.
-
D.
exSpouse
Indicates that two people were formerly married to each other but are no longer spouses.
-
E.
coSpouse
Indicates that two individuals are married to each other as spouses.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61f84f288190877116330bd54393 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:05 a.m.