Triple
T21054633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harapha |
E518676
|
entity |
| Predicate | workAuthorReligion |
P19416
|
FINISHED |
| Object | Protestant |
—
|
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: Protestant | Statement: [Harapha, workAuthorReligion, Protestant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workAuthorReligion Context triple: [Harapha, workAuthorReligion, Protestant]
-
A.
authorsReligion
chosen
Indicates the religious affiliation or belief system associated with an author.
-
B.
religionRelatedWork
Indicates that a work (such as a text, artwork, or project) is related to, concerned with, or produced in the context of a particular religion or religious tradition.
-
C.
founderOfReligionAssociated
Indicates that a person is the founder of a religion with which another entity is associated.
-
D.
associatedReligionText
Indicates that there is a textual work (such as a scripture or religious document) that is specifically associated with, or pertains to, a given religion.
-
E.
religiousFigure
Indicates that one entity is recognized or designated as a religious leader, authority, or sacred person in relation to another entity.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd7edb8481908e4dc7573f7fa98f |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:36 p.m.