Triple
T13958026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hedvig Eleonora of Holstein-Gottorp |
E335716
|
entity |
| Predicate | reign as queen consort |
P59097
|
FINISHED |
| Object | 1654–1660 |
—
|
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: 1654–1660 | Statement: [Hedvig Eleonora of Holstein-Gottorp, reign as queen consort, 1654–1660]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reign as queen consort Context triple: [Hedvig Eleonora of Holstein-Gottorp, reign as queen consort, 1654–1660]
-
A.
reignAsQueenConsort
chosen
Indicates that a person holds the position and performs the role of queen consort during the reign of a monarch.
-
B.
reignAsQueenConsortFrom
Indicates the time period during which a person held the role of queen consort, starting from a specified date or event.
-
C.
reignAsEmpressConsortBegan
Indicates the point in time when an individual began their tenure or role as an empress consort.
-
D.
reignAsQueenConsortOfEnglandEnd
Indicates the time or event at which an individual’s tenure as Queen Consort of England comes to an end.
-
E.
successorAsQueenConsort
Indicates that one individual became the next queen consort following another in a royal succession.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7a34f08190aa0d88b66154f268 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.