Triple
T7384264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Karelia |
E170340
|
entity |
| Predicate | hasTraditionalSongType |
P13181
|
FINISHED |
| Object | runo song |
—
|
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: runo song | Statement: [Western Karelia, hasTraditionalSongType, runo song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalSongType Context triple: [Western Karelia, hasTraditionalSongType, runo song]
-
A.
includesTraditionalSong
Indicates that one entity contains or features a traditional song as part of its content or composition.
-
B.
isTraditionallySungBy
Indicates that something, typically a song or chant, is customarily performed vocally by a particular person, group, or type of performer according to tradition.
-
C.
hasSongStyle
chosen
Indicates that an entity possesses, is characterized by, or is associated with a particular style or genre of song.
-
D.
hasTraditionalDance
Indicates that an entity is associated with, practices, or possesses a specific traditional dance.
-
E.
traditionallySungAfter
Indicates that one song or musical piece is customarily performed immediately following another in a cultural or traditional sequence.
- 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1efe1308190b96eefbff56140be |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:08 p.m.