Triple
T28369199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess of Albany |
E718577
|
entity |
| Predicate | spouseOfClaimant |
P13
|
FINISHED |
| Object | Charles Edward Stuart |
—
|
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: Charles Edward Stuart | Statement: [Countess of Albany, spouseOfClaimant, Charles Edward Stuart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfClaimant Context triple: [Countess of Albany, spouseOfClaimant, Charles Edward Stuart]
-
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.
spouseOfHead
Indicates that one person is the married partner of the individual who holds the position of head (e.g., head of a household, organization, or state).
-
C.
spouse
chosen
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
D.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
-
E.
spouseMember
Indicates that one entity is the spouse (married partner) of another entity.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 28, 2026, 12:58 a.m.