Triple
T21414143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukes of Pomerania |
E528254
|
entity |
| Predicate | dynastyEndCause |
P125302
|
FINISHED |
| Object | extinction of male line |
—
|
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: extinction of male line | Statement: [Dukes of Pomerania, dynastyEndCause, extinction of male line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyEndCause Context triple: [Dukes of Pomerania, dynastyEndCause, extinction of male line]
-
A.
dynastyDissolutionCause
chosen
Indicates the reason or factor that led to the dissolution or end of a dynasty.
-
B.
dynastyEndedWith
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
-
C.
endOfReignReason
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
-
D.
extinctDynasty
Indicates that a dynasty has ceased to exist and no longer continues through ruling descendants or recognized lineage.
-
E.
dynasticOutcome
Indicates the result or consequence of a succession or transfer of power within a dynasty, such as continuation, change, or end of a ruling line.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b2032fe48190907b282e2fffa2bd |
completed | April 22, 2026, 11:33 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:44 p.m.