Triple
T35093580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan II the Good |
E1012801
|
entity |
| Predicate | dynastyEndRole |
P59019
|
FINISHED |
| Object | last male of the Silesian Piasts |
—
|
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: last male of the Silesian Piasts | Statement: [Jan II the Good, dynastyEndRole, last male of the Silesian Piasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyEndRole Context triple: [Jan II the Good, dynastyEndRole, last male of the Silesian Piasts]
-
A.
dynastyEndedWith
chosen
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
-
B.
dynasticRole
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
-
C.
dynastyProvided
Indicates that a particular dynasty supplied, supported, or was responsible for providing something to another entity or context.
-
D.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
E.
dynastyDescribedAs
Indicates that a dynasty is characterized or labeled using a particular description, epithet, or qualitative phrase.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.