Triple
T16841542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Felpersham |
E409423
|
entity |
| Predicate | hasReligiousRoleInFiction |
P51786
|
FINISHED |
| Object | diocesan centre |
—
|
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: diocesan centre | Statement: [Felpersham, hasReligiousRoleInFiction, diocesan centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousRoleInFiction Context triple: [Felpersham, hasReligiousRoleInFiction, diocesan centre]
-
A.
religionOfCharacterPortrayed
Indicates that a work portrays a character as adhering to or being associated with a particular religion.
-
B.
hasReligiousCharacter
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
-
C.
hasReligiousRoleEquivalent
Indicates that two religious roles are considered functionally or hierarchically equivalent within or across religious traditions.
-
D.
religiousTextRole
Indicates the specific role or function that a religious text has in relation to a person, group, practice, or tradition.
-
E.
associatedReligionRole
chosen
Indicates that one entity holds a specific religious role, office, or function 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b35167a48190b45a459023e3ab1b |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.