Triple
T11501635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krug |
E272676
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Rada |
unclear NED1
|
NE 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: Rada | Statement: [Krug, relatedTo, Rada]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rada Context triple: [Krug, relatedTo, Rada]
-
A.
Rada
Rada is the commonly used short name for Ukraine’s unicameral national parliament, the Verkhovna Rada.
-
B.
Radicava
Radicava is a prescription medication containing edaravone, used to slow the progression of amyotrophic lateral sclerosis (ALS) in adults.
-
C.
Rendulic
Rendulic is a German-language surname most notably associated with Lothar Rendulic, an Austrian-born German army general during World War II.
-
D.
Kuban Rada
Kuban Rada was the governing council and political representative body of the Kuban Cossacks in the Kuban region during the turbulent years surrounding the Russian Revolution and Civil War.
-
E.
Rascia
Rascia is a historical region in the central Balkans that formed the medieval core of the Serbian state.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de55cbc8190be71c2d03dc044f2 |
completed | April 10, 2026, 2:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e604bc1d3c81908497f1d19dcc2167 |
completed | April 20, 2026, 10:49 a.m. |
Created at: April 8, 2026, 9:36 p.m.