Triple
T425677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belarusians |
E9601
|
entity |
| Predicate | associatedWithMusic |
P2152
|
FINISHED |
| Object | Belarusian music |
—
|
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: Belarusian music | Statement: [Belarusians, associatedWithMusic, Belarusian music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMusic Context triple: [Belarusians, associatedWithMusic, Belarusian music]
-
A.
associatedMusic
chosen
Indicates a relationship where one entity is linked to or connected with a piece of music, such as being used by, related to, or thematically tied to that music.
-
B.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
-
C.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
D.
associatedWithMovement
Indicates a relationship where an entity is connected to, involved in, or influenced by a particular movement (e.g., social, political, artistic, or ideological).
-
E.
musicDriven
Indicates that one entity’s behavior, structure, or progression is guided, influenced, or determined primarily by music or musical elements.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eed56ab481909eec289075496260 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.