Triple
T8137198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cossack dumas |
E190000
|
entity |
| Predicate | performedBy |
P1363
|
FINISHED |
| Object | kobzars |
E190001
|
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: kobzars | Statement: [Cossack dumas, performedBy, kobzars]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: kobzars Context triple: [Cossack dumas, performedBy, kobzars]
-
A.
kobzars
chosen
Kobzars were traditional Ukrainian itinerant bards, often blind, who sang epic and historical songs to the accompaniment of instruments like the kobza or bandura.
-
B.
Ershevka
Ershevka is a rural locality in Kaluga Oblast, Russia.
-
C.
Kobeliaky
Kobeliaky is a historic town in central Ukraine, located in Poltava Oblast along the Vorskla River.
-
D.
Vyazniki
Vyazniki is a historic town in western Russia known for its traditional architecture and location on the Klyazma River.
-
E.
Bachorze
Bachorze is a small settlement in northern Poland located near Lake Charzykowskie, known for its access to the surrounding lakes and forests of the Kashubian region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb440171d48190afa4a312ab19389c |
completed | March 31, 2026, 3:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc949d9c7c81908efb4880f9250166 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 5:35 p.m.