Triple
T2072868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henriette Adelaide of Savoy |
E44853
|
entity |
| Predicate | regencyEndTime |
P2721
|
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, regencyEndTime, 1676]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regencyEndTime Context triple: [Henriette Adelaide of Savoy, regencyEndTime, 1676]
-
A.
regency
Indicates that one entity exercises ruling authority on behalf of another, typically when the latter is unable to govern directly (such as due to minority, absence, or incapacity).
-
B.
coRegencyStart
Indicates the point in time when a joint rule or shared reign between two or more authorities begins.
-
C.
hasRegency
Indicates that one entity exercises regency authority or governing power on behalf of another, typically during the latter’s minority, incapacity, or absence.
-
D.
endOfReign
chosen
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
E.
endDateAsPrincipalRoyalResidence
Indicates the date on which a location ceased to serve as the primary royal residence.
- 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_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. |
Created at: March 4, 2026, 7:41 p.m.