Triple
T32389697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Белая Троицкая церковь |
E827634
|
entity |
| Predicate | относящийся праздник |
P134250
|
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.
relatedHoliday
Indicates that there is an association or connection between two holidays, such as thematic, temporal, cultural, or contextual relatedness.
-
B.
celebratedDay
Indicates that a particular day is observed, honored, or festively recognized in association with an entity or event.
-
C.
favoriteHoliday
Indicates that one entity is the preferred or most enjoyed holiday of another entity.
-
D.
isCelebratoryOf
Indicates that something expresses celebration, honor, or festive recognition directed toward a particular event, person, or occasion.
-
E.
celebrationAssociatedWith
chosen
Indicates a relationship where a celebration is connected to, linked with, or held in relation to a particular entity, event, or context.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1d48d048190b6bb79e26881adb7 |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:52 a.m.