Triple
T28710813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantina |
E729826
|
entity |
| Predicate | marriageToConstantiusGallus |
P177544
|
FINISHED |
| Object | political dynastic alliance |
—
|
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: political dynastic alliance | Statement: [Constantina, marriageToConstantiusGallus, political dynastic alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageToConstantiusGallus Context triple: [Constantina, marriageToConstantiusGallus, political dynastic alliance]
-
A.
marriedToEmperor
Indicates that one entity is the spouse of an emperor, signifying a marital relationship to a reigning or titled emperor.
-
B.
placeOfMarriageToEmpressMatilda
Indicates the location where an individual married Empress Matilda.
-
C.
marriageFormedBy
Indicates that a marriage relationship was created or brought into existence by a specific event, action, or process.
-
D.
succeededByInMarriageToHenryI
Indicates that one person became the subsequent spouse of Henry I, following a previous spouse in marriage to him.
-
E.
marriageDateToEmpressMatilda
Indicates the date on which an individual married Empress Matilda.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 28, 2026, 5:48 a.m.