Triple
T13096444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geoffrey V, Count of Anjou |
E310600
|
entity |
| Predicate | marriageDateToEmpressMatilda |
P108023
|
FINISHED |
| Object | 1128 |
—
|
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: 1128 | Statement: [Geoffrey V, Count of Anjou, marriageDateToEmpressMatilda, 1128]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageDateToEmpressMatilda Context triple: [Geoffrey V, Count of Anjou, marriageDateToEmpressMatilda, 1128]
-
A.
marriageToHenryIIDate
Indicates the date on which an entity entered into marriage with Henry II.
-
B.
marriageToEdwardTheConfessor
Indicates a marital relationship in which the subject is married to Edward the Confessor.
-
C.
succeededByInMarriageToHenryI
Indicates that one person became the subsequent spouse of Henry I, following a previous spouse in marriage to him.
-
D.
marriedToFutureMonarch
Indicates that one person is married to another person who will become a monarch in the future.
-
E.
marriageFormedBy
Indicates that a marriage relationship was created or brought into existence by a specific event, action, or process.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9814e88a0819088418c792ce7aa57 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:03 p.m.