Triple
T32389683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Белая Троицкая церковь |
E827634
|
entity |
| Predicate | имеет алтарь |
P15258
|
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.
hasAltar
chosen
Indicates that one entity possesses, contains, or includes an altar as part of its features or components.
-
B.
hasMainAltarFor
Indicates that a specific altar serves as the primary or central altar designated for a particular entity, such as a church, chapel, or religious space.
-
C.
hasAltarLocation
Indicates that an altar is situated at or associated with a specific location.
-
D.
hadAltarpieceBy
Indicates that an entity (typically a religious building or space) possessed or featured an altarpiece created by a specified artist or maker.
-
E.
hasSacristy
Indicates that a religious building includes or is associated with a sacristy (a room where sacred vessels, vestments, and liturgical items are kept and prepared).
- 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_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 12:52 a.m.