Triple
T36406646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Церковь Святого Архангела Михаила |
E896763
|
entity |
| Predicate | может иметь приход |
P148866
|
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.
mayIncorporate
chosen
Indicates that one entity is allowed or able to include, absorb, or integrate another entity as part of itself or its structure.
-
B.
hasPotential
Indicates that an entity possesses the capacity or possibility to develop, achieve, or exhibit a particular state, quality, or outcome in the future.
-
C.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
D.
beneficiaryMayHave
Indicates that a beneficiary is allowed or permitted to possess, receive, or be associated with something.
-
E.
имеетПереход
Indicates that one entity has or includes a passage, crossing, or transition leading to another entity.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:10 p.m.