Triple
T17728307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleksandar Ranković |
E442522
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Ranković |
—
|
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: Ranković | Statement: [Aleksandar Ranković, familyName, Ranković]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ranković Context triple: [Aleksandar Ranković, familyName, Ranković]
-
A.
Radovan
Radovan is a masculine given name of Slavic origin, commonly used in several Eastern European countries.
-
B.
Rajaković
Rajaković is a Serbian surname most notably associated with NBA coach Darko Rajaković.
-
C.
Aleksandar Ranković
chosen
Aleksandar Ranković was a prominent Yugoslav communist politician and close ally of Josip Broz Tito, known for his powerful role in the security apparatus and later dramatic political downfall.
-
D.
Vučinić
Vučinić is a South Slavic surname commonly found in countries such as Serbia, Montenegro, and Croatia.
-
E.
Radivojevič
Radivojevič is a Slavic surname most notably borne by Slovak former professional ice hockey player Branko Radivojevič.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e4ae5c8190a6f0743f7e74b5bf |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 10:08 a.m.