Triple
T24209163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superior General |
E600480
|
entity |
| Predicate | canHaveVicar |
P78575
|
FINISHED |
| Object | Vicar General |
—
|
NE NERFINISHED |
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: Vicar General | Statement: [Superior General, canHaveVicar, Vicar General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHaveVicar Context triple: [Superior General, canHaveVicar, Vicar General]
-
A.
hasVicariate
chosen
Indicates that one entity serves as a vicariate (a delegated or substitute authority or jurisdiction) for another entity.
-
B.
hasSuffraganBishop
Indicates that one bishop holds the position of suffragan (subordinate or assistant) bishop in relation to another bishop or ecclesiastical authority.
-
C.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
D.
hasClergyRequirement
Indicates that a role, position, or activity requires the person involved to be a member of the clergy or to hold a specific clerical status.
-
E.
hasChaplain
Indicates that an entity is served or attended to by a designated chaplain.
- 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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f282020a5881909df47f766c3ee7af |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:53 p.m.