Triple
T8277646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilian Aleppian Order |
E193585
|
entity |
| Predicate | clergyComposition |
P82459
|
FINISHED |
| Object | priests |
—
|
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: priests | Statement: [Basilian Aleppian Order, clergyComposition, priests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clergyComposition Context triple: [Basilian Aleppian Order, clergyComposition, priests]
-
A.
clergySystem
Indicates a relationship in which an organized religious institution or tradition has a structured system of clergy roles, ranks, or offices.
-
B.
clergyCountEstimate
Indicates an estimated number of clergy associated with a particular entity or context.
-
C.
clergyOrder
Indicates that an individual belongs to, or is formally associated with, a specific religious clerical order or denomination.
-
D.
clergyView
Indicates that a member of the clergy holds a particular opinion, perspective, or evaluative stance toward something.
-
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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ea3fb481908b59414702a5147e |
completed | March 31, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:51 p.m.