Triple
T15684027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Савиндан |
E380149
|
entity |
| Predicate | традиционални обичај |
P64101
|
FINISHED |
| Object | сечење славског колача |
—
|
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: сечење славског колача | Statement: [Савиндан, традиционални обичај, сечење славског колача]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: традиционални обичај Context triple: [Савиндан, традиционални обичај, сечење славског колача]
-
A.
establishedTradition
chosen
Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
-
B.
traditionAt
Indicates that a particular tradition is practiced, observed, or associated at a specific place or location.
-
C.
calendarTradition
Indicates a relationship where a calendar is based on, follows, or embodies a particular cultural, religious, or historical tradition.
-
D.
traditionAscribes
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
E.
traditionalSee
Indicates that one entity perceives or views another entity in a conventional or customary manner, following established norms or traditions.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f31b5b881908e46ecd9fc6048ab |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8c856c8190882330114f9a1a5f |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:43 a.m.