Triple
T425676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belarusians |
E9601
|
entity |
| Predicate | associatedWithFolklore |
P9595
|
FINISHED |
| Object | Belarusian folklore |
—
|
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 folklore | Statement: [Belarusians, associatedWithFolklore, Belarusian folklore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFolklore Context triple: [Belarusians, associatedWithFolklore, Belarusian folklore]
-
A.
linkedToMythology
chosen
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
B.
associatedCurse
Indicates that one entity is linked to, affected by, or bears responsibility for a particular curse related to another entity.
-
C.
mythologicalEvent
Indicates an event or occurrence that takes place within mythological narratives or traditions, often involving gods, heroes, or supernatural phenomena.
-
D.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
E.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
- 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.