Triple
T33618841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anne Catherine of Denmark |
E861201
|
entity |
| Predicate | spouseMonarch |
P194952
|
FINISHED |
| Object | Christian IV of Denmark and Norway |
—
|
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: Christian IV of Denmark and Norway | Statement: [Anne Catherine of Denmark, spouseMonarch, Christian IV of Denmark and Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseMonarch Context triple: [Anne Catherine of Denmark, spouseMonarch, Christian IV of Denmark and Norway]
-
A.
spouseIsMonarchOf
Indicates that a person's spouse holds the position of monarch (ruler) of a specified country or territory.
-
B.
spouseServedMonarch
Indicates that the spouse of a person held a position of service or duty to a monarch.
-
C.
spouseOfRoyalHouse
chosen
Indicates that one entity is the spouse or consort of a member of a royal house.
-
D.
spouseOfHeirToThrone
Indicates that one person is the married partner of an individual who is the heir to a throne.
-
E.
regentSpouse
Indicates that one person is the spouse of a regent, i.e., married to an individual who rules on behalf of a monarch or in place of the sovereign.
- 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 1, 2026, 1:41 a.m.