Triple
T27223403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leopold IV, Prince of Lippe |
E681340
|
entity |
| Predicate | successorAsHeadOfState |
P184583
|
FINISHED |
| Object | none (monarchy abolished) |
—
|
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: none (monarchy abolished) | Statement: [Leopold IV, Prince of Lippe, successorAsHeadOfState, none (monarchy abolished)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsHeadOfState Context triple: [Leopold IV, Prince of Lippe, successorAsHeadOfState, none (monarchy abolished)]
-
A.
succeededByAsHeadOfState
Indicates that one individual directly followed another in the role of head of state.
-
B.
successorSovereign
Indicates that one entity becomes the next ruling sovereign following another entity, inheriting their position of supreme authority.
-
C.
successorOfficeOfCoSovereign
Indicates that one office is the subsequent or replacement office to a previous co-sovereign office in a line of succession.
-
D.
successorInCountry
Indicates that one entity takes over a role, position, or function from another entity within the same country.
-
E.
successorRuler
Indicates that one ruler directly follows another in holding a position of authority or rule.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: April 27, 2026, 9:43 a.m.