Triple
T4708132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edith of Wessex |
E104441
|
entity |
| Predicate | marriageToEdwardTheConfessor |
P59098
|
FINISHED |
| Object | 1045 |
—
|
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: 1045 | Statement: [Edith of Wessex, marriageToEdwardTheConfessor, 1045]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageToEdwardTheConfessor Context triple: [Edith of Wessex, marriageToEdwardTheConfessor, 1045]
-
A.
marriedToFutureMonarch
Indicates that one person is married to another person who will become a monarch in the future.
-
B.
marriageToHenryIIDate
Indicates the date on which an entity entered into marriage with Henry II.
-
C.
marriageToHenryVIIIStatus
Indicates the status or condition of an entity’s marriage relationship to Henry VIII (e.g., current, former, annulled, pending, etc.).
-
D.
marriageToHenryVIIIConsummated
Indicates that the subject’s marriage to Henry VIII was physically consummated.
-
E.
engagementToHenryVIII
Indicates a formal betrothal or promise of marriage specifically to Henry VIII.
- 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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd680b06e881908de87edf815f3cc0 |
completed | March 20, 2026, 3:30 p.m. |
Created at: March 20, 2026, 1:17 p.m.