Triple
T11346678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archeparchy of Philadelphia of the Ukrainians |
E268731
|
entity |
| Predicate | hasTypeOfClergy |
P3092
|
FINISHED |
| Object | secular clergy |
—
|
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: secular clergy | Statement: [Archeparchy of Philadelphia of the Ukrainians, hasTypeOfClergy, secular clergy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfClergy Context triple: [Archeparchy of Philadelphia of the Ukrainians, hasTypeOfClergy, secular clergy]
-
A.
hasClergyType
chosen
Indicates the specific category or role of clergy associated with an entity.
-
B.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
C.
memberOfClergy
Indicates that one entity serves in an official religious or clerical role within a religious organization or institution.
-
D.
hasNotableClergyman
Indicates that an entity is associated with a clergyman who is distinguished or notable in some recognized way.
-
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.
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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80148e2048190a716b515d78efdd1 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e6f8aeb4819080476f16a69b2ee3 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.