Triple
T823969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter III of Russia |
E17810
|
entity |
| Predicate | spouseFrom |
P19982
|
FINISHED |
| Object | 1745 |
—
|
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: 1745 | Statement: [Peter III of Russia, spouseFrom, 1745]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseFrom Context triple: [Peter III of Russia, spouseFrom, 1745]
-
A.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
B.
spouseFamily
Indicates a family relationship formed through marriage, such as between a person and their spouse’s relatives.
-
C.
spouseMemberOf
Indicates that a person’s spouse is a member of a specified group, organization, or entity.
-
D.
metSpouseThrough
Indicates that one person became acquainted with and subsequently married their spouse as a result of a particular intermediary person, event, place, or context.
-
E.
spouseOrLover
Indicates a romantic partnership between two entities, whether formalized as a spouse or existing as a lover.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab7d3984819089aefbf12d3b3c2c |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa781e1081909df006f730296c53 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4781c88190ae36906251347cdc |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:38 p.m.