Triple
T25987634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Christian Hero |
E646243
|
entity |
| Predicate | clergyStatusOfAuthor |
P82133
|
FINISHED |
| Object | Anglican clergyman |
—
|
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: Anglican clergyman | Statement: [The Christian Hero, clergyStatusOfAuthor, Anglican clergyman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clergyStatusOfAuthor Context triple: [The Christian Hero, clergyStatusOfAuthor, Anglican clergyman]
-
A.
writtenByClergyOrTheologian
Indicates that the work or text was authored by a member of the clergy or a professional theologian.
-
B.
religiousAuthorityStatus
Indicates the role or level of recognized authority an entity holds within a religious or spiritual hierarchy.
-
C.
clergyCan
Indicates that members of the clergy are permitted or authorized to perform a specified action or exercise a particular role or function.
-
D.
hasClergyType
Indicates the specific category or role of clergy associated with an entity.
-
E.
memberOfClergy
chosen
Indicates that one entity serves in an official religious or clerical role within a religious organization or institution.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60545933081908d733c7bc49009f1 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:55 a.m.