Triple
T32389677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Белая Троицкая церковь |
E827634
|
entity |
| Predicate | посвящена |
P69507
|
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.
dedicatee
Indicates the person or entity to whom a work, such as a book, artwork, or performance, is formally dedicated.
-
B.
dedicatedToConcept
chosen
Indicates that something is specifically devoted, committed, or purposefully directed toward a particular concept or abstract idea.
-
C.
dedicated
Indicates that one entity is formally assigned, reserved, or committed for the specific use, benefit, or purpose of another entity.
-
D.
повʼязанеЗ
Indicates a general association or connection between one entity and another.
-
E.
dedicatesLifeTo
Indicates devoting one’s time, effort, and primary purpose over an extended period to a particular person, cause, goal, or activity.
- 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_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:52 a.m.