Triple
T25894402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louise of Mecklenburg-Güstrow |
E652426
|
entity |
| Predicate | reign as queen consort of Norway ended |
P35170
|
FINISHED |
| Object | 1721 |
—
|
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: 1721 | Statement: [Louise of Mecklenburg-Güstrow, reign as queen consort of Norway ended, 1721]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reign as queen consort of Norway ended Context triple: [Louise of Mecklenburg-Güstrow, reign as queen consort of Norway ended, 1721]
-
A.
reignAsQueenConsortNorwayEnd
chosen
Indicates the time or event at which an individual’s tenure as queen consort of Norway comes to an end.
-
B.
reignAsQueenConsortNorwayStart
Indicates the time at which an individual began serving as queen consort of Norway.
-
C.
reignAsQueenConsortDenmarkEnd
Indicates the date or point in time when an individual’s tenure as queen consort of Denmark came to an end.
-
D.
reignAsPrincessConsortEnd
Indicates the time or event at which an individual’s tenure as princess consort comes to an end.
-
E.
reignAsKingConsortEnd
Indicates the point in time or event at which an individual’s tenure as king consort comes to an end.
- 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_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 22, 2026, 8:22 a.m.