Triple
T8111505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donskoy Monastery |
E189363
|
entity |
| Predicate | hasGateChurch |
P39232
|
FINISHED |
| Object | gate churches with icons of the Theotokos |
—
|
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: gate churches with icons of the Theotokos | Statement: [Donskoy Monastery, hasGateChurch, gate churches with icons of the Theotokos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGateChurch Context triple: [Donskoy Monastery, hasGateChurch, gate churches with icons of the Theotokos]
-
A.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
B.
hasChurchType
Indicates that one entity (typically a church) is classified as being of a particular church type or category.
-
C.
isGuildChurchFor
Indicates that a church serves as the designated place of worship or official church for a particular guild or professional association.
-
D.
hasChurchFeature
chosen
Indicates that a church possesses or includes a particular architectural, functional, or structural feature.
-
E.
hasMemberChurch
Indicates that a particular church is a constituent member of a larger religious organization, denomination, or church body.
- 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4664fef881908b0dc7b158aca398 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb368e7f4c81909aabd7716f0de79d |
completed | March 31, 2026, 2:50 a.m. |
Created at: March 30, 2026, 5:32 p.m.