Triple
T21837959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svetozar Boroević von Bojna |
E539170
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Svetozar |
—
|
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: Svetozar | Statement: [Svetozar Boroević von Bojna, givenName, Svetozar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Svetozar Context triple: [Svetozar Boroević von Bojna, givenName, Svetozar]
-
A.
Svetozar Boroević
chosen
Svetozar Boroević was an Austro-Hungarian field marshal renowned for his defensive leadership on the Italian Front during World War I.
-
B.
Stjepan
Stjepan is a Croatian masculine given name, equivalent to Stephen, commonly borne by notable figures in Croatian history and politics.
-
C.
Đorđe
Đorđe is the given name of Karađorđe Petrović, the Serbian revolutionary leader who founded the Karađorđević dynasty.
-
D.
Dragoljub
Dragoljub is a masculine given name of Slavic origin, commonly used in Serbia and other South Slavic countries.
-
E.
Milutin
Milutin is a masculine given name of Slavic origin, commonly used in Serbian and other South Slavic cultures.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7a9a36881909eb917f12d061ba9 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 16, 2026, 6:55 p.m.