Triple
T5583356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adeliza of Louvain |
E146691
|
entity |
| Predicate | succeededByInMarriageToHenryI |
P64891
|
FINISHED |
| Object | none (Henry I died in 1135) |
—
|
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: none (Henry I died in 1135) | Statement: [Adeliza of Louvain, succeededByInMarriageToHenryI, none (Henry I died in 1135)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededByInMarriageToHenryI Context triple: [Adeliza of Louvain, succeededByInMarriageToHenryI, none (Henry I died in 1135)]
-
A.
marriageToEdwardTheConfessor
Indicates a marital relationship in which the subject is married to Edward the Confessor.
-
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.
marriedToFutureMonarch
Indicates that one person is married to another person who will become a monarch in the future.
-
E.
marriageToHenryVIIIConsummated
Indicates that the subject’s marriage to Henry VIII was physically consummated.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02084b5f0819089b62283c57704ec |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:37 p.m.