Triple
T6516399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fraternitas Sacerdotalis Sancti Pii X |
E148273
|
entity |
| Predicate | hasPriestlySocietyType |
P31566
|
FINISHED |
| Object | society of apostolic life (claimed) |
—
|
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: society of apostolic life (claimed) | Statement: [Fraternitas Sacerdotalis Sancti Pii X, hasPriestlySocietyType, society of apostolic life (claimed)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPriestlySocietyType Context triple: [Fraternitas Sacerdotalis Sancti Pii X, hasPriestlySocietyType, society of apostolic life (claimed)]
-
A.
hasClergyType
Indicates the specific category or role of clergy associated with an entity.
-
B.
hasReligiousInstitutionType
chosen
Indicates that an entity is associated with, or classified by, a specific type of religious institution.
-
C.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
D.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
-
E.
hasClergyOrder
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac0d395081908fe6b1f9a912f095 |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.