Triple
T27070330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baldwin I, Margrave of Flanders |
E685306
|
entity |
| Predicate | spousePreviouslyMarriedTo |
P139882
|
FINISHED |
| Object | Æthelwulf, King of Wessex |
—
|
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: Æthelwulf, King of Wessex | Statement: [Baldwin I, Margrave of Flanders, spousePreviouslyMarriedTo, Æthelwulf, King of Wessex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spousePreviouslyMarriedTo Context triple: [Baldwin I, Margrave of Flanders, spousePreviouslyMarriedTo, Æthelwulf, King of Wessex]
-
A.
spouseLaterMarriedBy
Indicates that one’s spouse subsequently entered into a later marriage with another partner.
-
B.
marriedBefore
Indicates that one entity entered into a marriage at an earlier time than the other entity.
-
C.
subsequentSpouse
chosen
Indicates that one person is a later spouse of another, following a previous marriage involving at least one of them.
-
D.
exSpouse
Indicates that two people were formerly married to each other but are no longer spouses.
-
E.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 8:27 a.m.