Triple
T28269962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Holland (betrothed) |
E712818
|
entity |
| Predicate | prospectiveSpouse |
P121005
|
FINISHED |
| Object | Anne of York |
—
|
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: Anne of York | Statement: [Henry Holland (betrothed), prospectiveSpouse, Anne of York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prospectiveSpouse Context triple: [Henry Holland (betrothed), prospectiveSpouse, Anne of York]
-
A.
intendedSpouse
chosen
Indicates that one person is planned or expected to become the spouse of another, typically through an intended or future marriage.
-
B.
possiblySpouse
Indicates that two entities may be spouses, reflecting an uncertain or hypothesized marital relationship between them.
-
C.
proposedBride
Indicates that one entity has been put forward or suggested as a potential bride for another entity.
-
D.
isProspectiveDaughterInLawOf
Indicates that one person is expected or intended to become the daughter-in-law of another person, typically through a planned or anticipated marriage to that person's child.
-
E.
destinedToMarry
Indicates that two entities are fated or predetermined to marry each other in the future.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64420b9a08190a15d872eb1a130c9 |
completed | May 2, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:17 p.m.