Triple
T35289845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenneth Parnell |
E1019189
|
entity |
| Predicate | religionClaim |
P10912
|
FINISHED |
| Object | claimed to be a minister |
—
|
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: claimed to be a minister | Statement: [Kenneth Parnell, religionClaim, claimed to be a minister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionClaim Context triple: [Kenneth Parnell, religionClaim, claimed to be a minister]
-
A.
religiousClaim
chosen
Indicates that an entity asserts, expresses, or is associated with a statement or belief grounded in religion or spiritual doctrine.
-
B.
allegedReligion
Indicates that one entity is claimed or reported to be associated with a particular religion, without asserting that the claim is true.
-
C.
doctrinalClaim
Indicates that an entity asserts or upholds a specific doctrinal or belief-based proposition as true.
-
D.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
E.
bearerReligion
Indicates that a bearer (such as a person or entity) adheres to, practices, or is associated with a particular religion.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:03 p.m.