Triple
T34559127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Raspe, Landgrave of Thuringia |
E887288
|
entity |
| Predicate | reignAsAntiKingEnd |
P109570
|
FINISHED |
| Object | 16 February 1247 |
—
|
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: 16 February 1247 | Statement: [Henry Raspe, Landgrave of Thuringia, reignAsAntiKingEnd, 16 February 1247]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsAntiKingEnd Context triple: [Henry Raspe, Landgrave of Thuringia, reignAsAntiKingEnd, 16 February 1247]
-
A.
reignAsAntiKingStart
Indicates the point in time when an individual begins an illegitimate or rival reign as an anti-king in opposition to a recognized monarch.
-
B.
reignAsKingEnd
chosen
Indicates the point in time or event at which an entity’s period of reigning as king comes to an end.
-
C.
reignAs
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
D.
reignAsHeirApparentEnd
Indicates the point in time or event at which an individual’s period of serving as heir apparent to a throne or title comes to an end.
-
E.
reignWith
Indicates that one entity rules or holds sovereign authority jointly alongside another entity.
- 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 1, 2026, 2:02 a.m.