Triple
T26006495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Света Неделя |
E646773
|
entity |
| Predicate | посветенаНа |
P24360
|
FINISHED |
| Object | Света Неделя (светица) |
—
|
NE NERFINISHED |
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.
познатПо
Indicates that an entity is known or recognized for a particular quality, achievement, role, or characteristic.
-
B.
dedicatee
chosen
Indicates the person or entity to whom a work, such as a book, artwork, or performance, is formally dedicated.
-
C.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
-
D.
dedicatedOnOccasionOf
Indicates that something (typically a work, object, or event) is formally dedicated in connection with or to commemorate a particular occasion.
-
E.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6057bd2708190bf400b153aca2f1b |
completed | May 2, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9 a.m.