Triple

T19489478
Position Surface form Disambiguated ID Type / Status
Subject Miloš Kobilić E487608 entity
Predicate roleInBattleOfKosovo P108011 FINISHED
Object assassin of the Ottoman sultan 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: assassin of the Ottoman sultan | Statement: [Miloš Kobilić, roleInBattleOfKosovo, assassin of the Ottoman sultan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfKosovo
Context triple: [Miloš Kobilić, roleInBattleOfKosovo, assassin of the Ottoman sultan]
  • A. roleInWarOrConflict chosen
    Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
  • B. roleInMalmedyMassacre
    Indicates that an entity participated in, contributed to, or was otherwise involved in the Malmedy Massacre.
  • C. foughtAs
    Indicates that an entity participated in a conflict or war in the capacity, role, or identity specified by another entity.
  • D. roleInMontenegro
    Indicates that an entity holds or has held an official role, position, or function within the country of Montenegro.
  • E. roleInLibyanCivilWar
    Indicates the specific involvement, function, or position an entity had in the context of the Libyan Civil War.
  • F. None of above.

Provenance (3 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_69d8e8d924388190b847cb15bb3d0aff completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6348ad4088190b530f47efca90165 completed April 20, 2026, 2:13 p.m.
PD Predicate disambiguation batch_69e4fd7883308190b73912a71a35a835 completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 1:39 p.m.