Triple
T16276663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Council of the Russian Orthodox Church |
E395145
|
entity |
| Predicate | includesLaity |
P122480
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Local Council of the Russian Orthodox Church, includesLaity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLaity Context triple: [Local Council of the Russian Orthodox Church, includesLaity, true]
-
A.
hasViewOnLaity
Indicates that one entity holds a particular stance, opinion, or doctrinal position regarding the role or nature of laypeople.
-
B.
hasLayMinistry
Indicates that an entity participates in or is associated with a lay (non-ordained) ministry role or service within a religious context.
-
C.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
D.
involvesClergy
Indicates that the situation, event, or action includes the participation or presence of clergy members.
-
E.
clergyCan
Indicates that members of the clergy are permitted or authorized to perform a specified action or exercise a particular role or function.
- F. None of above. chosen
Provenance (4 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2460ea5a4819099f779288a754c8d |
completed | April 17, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:05 a.m.