Triple
T12160617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Stewart, 1st Lord Methven |
E289694
|
entity |
| Predicate | spouseOrderWithMargaretTudor |
P4764
|
FINISHED |
| Object | third husband |
—
|
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: third husband | Statement: [Henry Stewart, 1st Lord Methven, spouseOrderWithMargaretTudor, third husband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOrderWithMargaretTudor Context triple: [Henry Stewart, 1st Lord Methven, spouseOrderWithMargaretTudor, third husband]
-
A.
orderInSequenceOfHenryVIIIWives
Indicates the numerical position that a given wife occupies in the ordered sequence of Henry VIII’s wives.
-
B.
spouseOrder
chosen
Indicates the position or sequence of a person among multiple spouses in a marital relationship.
-
C.
marriageToHenryVIIIStatus
Indicates the status or condition of an entity’s marriage relationship to Henry VIII (e.g., current, former, annulled, pending, etc.).
-
D.
marriedToFutureMonarch
Indicates that one person is married to another person who will become a monarch in the future.
-
E.
marriageToHenryIIDate
Indicates the date on which an entity entered into marriage with Henry II.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.