Triple
T4109237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquess of Ormonde |
E88527
|
entity |
| Predicate | traditionalReligionOfHolders |
P23795
|
FINISHED |
| Object | Roman Catholic |
—
|
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: Roman Catholic | Statement: [Marquess of Ormonde, traditionalReligionOfHolders, Roman Catholic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalReligionOfHolders Context triple: [Marquess of Ormonde, traditionalReligionOfHolders, Roman Catholic]
-
A.
titleHolderReligion
chosen
Indicates the religious affiliation associated with the holder of a particular title.
-
B.
officialReligion
Indicates that a particular religion is formally recognized and designated as the official or state religion of an entity (such as a country or region).
-
C.
traditionalReligionName
Indicates that an entity has a name specifically associated with a traditional or indigenous religion.
-
D.
previousReligionOfKingdom
Indicates that a specified religion was formerly practiced or officially adopted by a kingdom before being replaced or superseded.
-
E.
foundedReligion
Indicates that an entity established or originated 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:40 p.m.