Triple
T33447833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Messenger |
E856554
|
entity |
| Predicate | religiousOfficeType |
P70093
|
FINISHED |
| Object | charismatic leadership title |
—
|
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: charismatic leadership title | Statement: [The Messenger, religiousOfficeType, charismatic leadership title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousOfficeType Context triple: [The Messenger, religiousOfficeType, charismatic leadership title]
-
A.
denominationalOfficeType
Indicates the specific type or category of official position held within a religious denomination.
-
B.
religiousWorkType
Indicates the specific type or category of religious work or activity associated with an entity.
-
C.
religiousServiceType
Indicates the specific kind or category of religious service associated with an event or context.
-
D.
ecclesiasticalType
Indicates the specific ecclesiastical category or classification that applies to a religious entity within a church hierarchy.
-
E.
religiousFigureType
chosen
Indicates the specific role or category of a person recognized as a religious figure (e.g., priest, monk, prophet) within a religious context.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
Created at: May 1, 2026, 1:37 a.m.