Triple
T29702185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peada of Mercia |
E751517
|
entity |
| Predicate | convertedForMarriageTo |
P137120
|
FINISHED |
| Object | Alhflæd of Northumbria |
—
|
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: Alhflæd of Northumbria | Statement: [Peada of Mercia, convertedForMarriageTo, Alhflæd of Northumbria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedForMarriageTo Context triple: [Peada of Mercia, convertedForMarriageTo, Alhflæd of Northumbria]
-
A.
marriesFor
Indicates that one entity enters into marriage with another entity specifically for a particular reason, motive, or benefit.
-
B.
marriedInto
Indicates that one entity became connected to another’s family or group through marriage, rather than by birth or prior membership.
-
C.
resultedInMarriageTo
chosen
Indicates that one event, action, or circumstance led to or caused a marriage to occur between the related entities.
-
D.
marriageFormedBy
Indicates that a marriage relationship was created or brought into existence by a specific event, action, or process.
-
E.
regardsMarriageAs
Indicates that one entity holds a particular view, attitude, or evaluative stance toward the institution or concept of marriage.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 7:24 p.m.