Triple
T31619388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Belgrade (1456) |
E806851
|
entity |
| Predicate | HunyadiRole |
P172025
|
FINISHED |
| Object | military leader of the defense |
—
|
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: military leader of the defense | Statement: [Siege of Belgrade (1456), HunyadiRole, military leader of the defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HunyadiRole Context triple: [Siege of Belgrade (1456), HunyadiRole, military leader of the defense]
-
A.
MongolianCommander
Indicates that an individual holds a commanding or leadership role within a Mongolian military or armed force context.
-
B.
roleInAlexiad
Indicates that one entity has a specific role or function within the context of the Alexiad (e.g., as an author, subject, or referenced figure).
-
C.
ZawiszaRole
Indicates that an entity holds or is assigned a specific role or function within the Zawisza context.
-
D.
successorAsKingOfHungary
Indicates that one person became the next king of Hungary following another person in the royal succession.
-
E.
commanderOfWallachia
Indicates that one entity serves as the military commander responsible for the forces or defense of Wallachia.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:40 p.m.