Triple
T36040343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stefan Radoslav |
E1042521
|
entity |
| Predicate | successorAsKingOfSerbia |
P202037
|
FINISHED |
| Object | Stefan Vladislav |
—
|
NE NERFINISHED |
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: Stefan Vladislav | Statement: [Stefan Radoslav, successorAsKingOfSerbia, Stefan Vladislav]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsKingOfSerbia Context triple: [Stefan Radoslav, successorAsKingOfSerbia, Stefan Vladislav]
-
A.
proclaimedKingdomOfSerbia
Indicates that an entity formally declared or announced the establishment or existence of the Kingdom of Serbia.
-
B.
successorAsKingOfHungary
Indicates that one person became the next king of Hungary following another person in the royal succession.
-
C.
successorAsDukeOfAustria
Indicates that one entity became the next holder of the title Duke of Austria after another entity.
-
D.
successorAsEmperorOfAustria
Indicates that one person became the next Emperor of Austria following another person in the line of succession.
-
E.
successorAsKingOfItaly
Indicates that one person became the next king of Italy after another person.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
| PDg | Predicate description generation | batch_6a004868cf308190a2a93c32c92f22d9 |
completed | May 10, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:07 p.m.