Triple
T23682669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luise Eleonore of Hohenlohe-Langenburg |
E585069
|
entity |
| Predicate | regencyEndDate |
P101390
|
FINISHED |
| Object | 1821 |
—
|
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: 1821 | Statement: [Luise Eleonore of Hohenlohe-Langenburg, regencyEndDate, 1821]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regencyEndDate Context triple: [Luise Eleonore of Hohenlohe-Langenburg, regencyEndDate, 1821]
-
A.
regencyEnded
Indicates that a period during which one party governed on behalf of another (a regency) has come to an end.
-
B.
regencyEndYear
chosen
Indicates the calendar year in which a regency—rule exercised on behalf of another, typically a monarch—comes to an end.
-
C.
regencyEndApprox
Indicates that the end of a regency period is known only approximately rather than as an exact date.
-
D.
regencyBeganAfter
Indicates that the start of one regency occurred later in time than the start of another regency.
-
E.
regencyBegan
Indicates the point in time when a regency—rule exercised on behalf of another, typically a monarch—officially started.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f93dd081909040ff117a82b87e |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:51 p.m.