Triple
T23438675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Orthodox Church properties in Moscow |
E565336
|
entity |
| Predicate | majorMonastery |
P19162
|
FINISHED |
| Object | Novospassky Monastery |
—
|
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: Novospassky Monastery | Statement: [Russian Orthodox Church properties in Moscow, majorMonastery, Novospassky Monastery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorMonastery Context triple: [Russian Orthodox Church properties in Moscow, majorMonastery, Novospassky Monastery]
-
A.
importantMonastery
chosen
Indicates that a monastery holds significant religious, historical, or cultural importance relative to others.
-
B.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
-
C.
monasteryType
Indicates the specific kind or classification of a monastery in relation to its broader religious or organizational category.
-
D.
containsMonastery
Indicates that one entity includes or encompasses a monastery within its boundaries or composition.
-
E.
monasteryName
Indicates the name assigned to a monastery as its identifying label.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5de713c8190b35bfa66dddbd5af |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:50 p.m.