Triple
T31984635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Vilhelmine Marie of Denmark |
E816685
|
entity |
| Predicate | spouseTitleOfKarl |
P17687
|
FINISHED |
| Object | Duke of Schleswig-Holstein-Sonderburg-Glücksburg |
—
|
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: Duke of Schleswig-Holstein-Sonderburg-Glücksburg | Statement: [Princess Vilhelmine Marie of Denmark, spouseTitleOfKarl, Duke of Schleswig-Holstein-Sonderburg-Glücksburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseTitleOfKarl Context triple: [Princess Vilhelmine Marie of Denmark, spouseTitleOfKarl, Duke of Schleswig-Holstein-Sonderburg-Glücksburg]
-
A.
spouseNameWithTitle
Indicates that a person’s spouse is identified by name together with an associated honorific or title.
-
B.
isSpouseOfTitle
Indicates that one entity holds a spousal relationship specifically associated with a titled or honorific status of another entity.
-
C.
hasSpouseTitle
chosen
Indicates that a person’s spouse holds a particular title or honorific designation.
-
D.
currentTitleHolderSpouseOf
Indicates that one entity is the current spouse of the individual who presently holds a specified title.
-
E.
spouseAlsoKnownAs
Indicates that a person’s spouse is referred to by an alternative name or alias.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 1, 2026, 12:12 a.m.