Triple

T31984607
Position Surface form Disambiguated ID Type / Status
Subject Princess Vilhelmine Marie of Denmark E816685 entity
Predicate endTimeOfSpouseRelationshipWithFrederickVII P149185 FINISHED
Object 1837 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: 1837 | Statement: [Princess Vilhelmine Marie of Denmark, endTimeOfSpouseRelationshipWithFrederickVII, 1837]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: endTimeOfSpouseRelationshipWithFrederickVII
Context triple: [Princess Vilhelmine Marie of Denmark, endTimeOfSpouseRelationshipWithFrederickVII, 1837]
  • A. marriageToFrederickIV
    Indicates a marital relationship in which the subject is married to Frederick IV.
  • B. marriageOrderWithFrederickVII
    Indicates the sequence or order in which an entity entered into marriage with Frederick VII.
  • C. endTimeOfMarriageWithPeterIII
    Indicates the date and time when a marriage involving Peter III officially ended.
  • D. marriedToMonarchUntil chosen
    Indicates that an individual was married to a monarch up to a specified end point in time, after which the marriage no longer held.
  • E. marriageYearToKing
    Indicates the year in which an entity entered into marriage with a king.
  • 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_69fd884cb2b48190b6acd473430d9e19 completed May 8, 2026, 6:53 a.m.
PD Predicate disambiguation batch_69fd8709ca208190a8bab836f0156af5 completed May 8, 2026, 6:47 a.m.
Created at: May 1, 2026, 12:12 a.m.