Triple
T22863740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Adelaide Mary Louisa |
E566993
|
entity |
| Predicate | reignAsGermanEmpressEnd |
P150017
|
FINISHED |
| Object | 1888-06-15 |
—
|
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: 1888-06-15 | Statement: [Victoria Adelaide Mary Louisa, reignAsGermanEmpressEnd, 1888-06-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsGermanEmpressEnd Context triple: [Victoria Adelaide Mary Louisa, reignAsGermanEmpressEnd, 1888-06-15]
-
A.
reignAsQueenConsortOfGermanyEnd
Indicates the time or event at which an individual’s tenure as queen consort of Germany comes to an end.
-
B.
reignEndAsGermanEmperor
Indicates the time or event at which an individual's period of ruling as German Emperor comes to an end.
-
C.
reignAsKingOfGermanyEnd
Indicates the time or event at which an individual’s tenure as king of Germany comes to an end.
-
D.
reignEndAsKingOfBavaria
Indicates the time or event at which an individual's period of ruling as king of Bavaria comes to an end.
-
E.
reignAsHolyRomanEmpressConsortEnd
Indicates the time or event at which an individual’s tenure as Holy Roman Empress consort comes to an end.
- F. None of above. chosen
Provenance (4 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eff1c18819081dc9dfc1816f746 |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:38 p.m.