Triple

T23329838
Position Surface form Disambiguated ID Type / Status
Subject Despot Jovan Uglješa E591413 entity
Predicate relative P37 FINISHED
Object Prince Marko 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: Prince Marko | Statement: [Despot Jovan Uglješa, relative, Prince Marko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Prince Marko
Context triple: [Despot Jovan Uglješa, relative, Prince Marko]
  • A. Prince Marko (Kraljević Marko) chosen
    Prince Marko (Kraljević Marko) is a legendary Serbian folk hero and epic knight famed in South Slavic oral tradition for his superhuman strength, chivalry, and resistance against Ottoman rule.
  • B. Marko
    Marko is a masculine given name, commonly used in Slavic and other European cultures, that is cognate with the name Marcus.
  • C. Gavrilo
    Gavrilo is a masculine given name of Slavic origin, commonly used in South Slavic countries and related to the name Gabriel.
  • D. Dragan
    Dragan is a common South Slavic male given name, especially prevalent in Serbia and neighboring countries.
  • E. Prince Lazar of Serbia
    Prince Lazar of Serbia was a 14th-century Serbian ruler and national hero best known for leading Serbian forces against the Ottoman Empire at the Battle of Kosovo in 1389.
  • 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_69e25d1effe4819096907f95f610dbff completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f197ec22a481908247f5f86acb6ab4 completed April 29, 2026, 5:32 a.m.
Created at: April 17, 2026, 5:14 p.m.