Triple
T18132528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry I, Prince of Anhalt |
E434048
|
entity |
| Predicate | end of reign |
P2721
|
FINISHED |
| Object | 1252 |
—
|
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: 1252 | Statement: [Henry I, Prince of Anhalt, end of reign, 1252]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: end of reign Context triple: [Henry I, Prince of Anhalt, end of reign, 1252]
-
A.
endOfReign
chosen
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
B.
endOfReignReason
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
-
C.
thirdHolderReignEnd
Indicates the date or point in time when the reign or tenure of the third holder of a title, office, or position comes to an end.
-
D.
culminationOfPower
Indicates a relationship where one entity represents the peak, final concentration, or ultimate expression of another entity’s power or influence.
-
E.
appliesAfterReignOf
Indicates that something becomes relevant, valid, or in effect only after the reign or rule of a specified entity has ended.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddf2c68881909dfbe59df15ddccc |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.