Triple
T2191099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poglavnik |
E49861
|
entity |
| Predicate | successorTitleInModernCroatia |
P36648
|
FINISHED |
| Object | none |
—
|
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 | Statement: [Poglavnik, successorTitleInModernCroatia, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorTitleInModernCroatia Context triple: [Poglavnik, successorTitleInModernCroatia, none]
-
A.
successorInAustria
Indicates that one entity directly follows another in a succession or sequence specifically within the context of Austria (e.g., in an office, role, or position).
-
B.
successorTitle
Indicates the title or position that directly follows and replaces a previous one in a sequence or succession.
-
C.
successorAsKingOfBohemia
Indicates that one person became the next king of Bohemia after another person.
-
D.
successorAsHolyRomanEmperor
Indicates that one entity directly follows another in holding the title of Holy Roman Emperor.
-
E.
successorTitleIntegratedInto
Indicates that the title of a successor entity has been merged into and is now part of another title or entity.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf3f5e008190beda3ce5d77209e0 |
completed | March 7, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbea8bd4881908f72019a5acf6174 |
completed | March 7, 2026, 5:59 a.m. |
Created at: March 4, 2026, 7:46 p.m.