Triple

T25894399
Position Surface form Disambiguated ID Type / Status
Subject Louise of Mecklenburg-Güstrow E652426 entity
Predicate reign as queen consort of Denmark started P35167 FINISHED
Object 1699 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: 1699 | Statement: [Louise of Mecklenburg-Güstrow, reign as queen consort of Denmark started, 1699]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reign as queen consort of Denmark started
Context triple: [Louise of Mecklenburg-Güstrow, reign as queen consort of Denmark started, 1699]
  • A. reignAsQueenConsortDenmarkStart chosen
    Indicates the date or point in time when an individual began serving as queen consort of Denmark.
  • B. reignAsQueenConsortDenmarkEnd
    Indicates the date or point in time when an individual’s tenure as queen consort of Denmark came to an end.
  • C. reignAsQueenConsortSwedenStart
    Indicates the time at which an individual began serving as queen consort of Sweden.
  • D. reignAsQueenConsortOfEnglandStart
    Indicates the time at which an individual began serving as queen consort of England to a reigning English monarch.
  • E. reignAsQueenConsortNorwayStart
    Indicates the time at which an individual began serving as queen consort of Norway.
  • 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_69e7ab3c6cc081908de59bfcc28ec19d completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f61f12b0f08190bc4a16907941864c completed May 2, 2026, 3:58 p.m.
PD Predicate disambiguation batch_69f61b37a5648190b10d33ae205ccfee completed May 2, 2026, 3:41 p.m.
Created at: April 22, 2026, 8:22 a.m.