Triple
T31142840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Upper Ossory |
E793835
|
entity |
| Predicate | laterReligionOfSomeHolders |
P23796
|
FINISHED |
| Object | Anglicanism |
—
|
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: Anglicanism | Statement: [Baron Upper Ossory, laterReligionOfSomeHolders, Anglicanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterReligionOfSomeHolders Context triple: [Baron Upper Ossory, laterReligionOfSomeHolders, Anglicanism]
-
A.
titleHolderReligion
Indicates the religious affiliation associated with the holder of a particular title.
-
B.
headOfReligion
Indicates that one entity serves as the supreme leader or highest authority of a particular religion or religious organization.
-
C.
titleHolderLaterReligion
chosen
Indicates that the person holding a particular title at a later time follows a specified religion.
-
D.
eraOfReligiousFunction
Indicates the historical time period during which a religious role, office, or function was actively performed or held.
-
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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: April 29, 2026, 9:06 p.m.