Triple
T2072852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henriette Adelaide of Savoy |
E44853
|
entity |
| Predicate | spouseEndTime |
P34761
|
FINISHED |
| Object | 1676 |
—
|
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: 1676 | Statement: [Henriette Adelaide of Savoy, spouseEndTime, 1676]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseEndTime Context triple: [Henriette Adelaide of Savoy, spouseEndTime, 1676]
-
A.
spouseStartTime
Indicates the point in time when two individuals began their spousal (marriage) relationship.
-
B.
spouseRelationshipEnd
Indicates that a marital relationship between two individuals has ended, such as through divorce, annulment, or separation.
-
C.
metSpouseAt
Indicates that one person first encountered or became acquainted with their spouse at a particular place, event, or time.
-
D.
spouseExecutionYear
Indicates the calendar year in which a person's spouse was executed.
-
E.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
- 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba0eaa5081908f6d6ff80f79b1c9 |
completed | March 7, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69abb7b0edac8190a58eabee55f73deb |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:41 p.m.