Triple
T32366026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redmen |
E826992
|
entity |
| Predicate | usedByReligiousAffiliation |
P56479
|
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: [Redmen, usedByReligiousAffiliation, Roman Catholic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByReligiousAffiliation Context triple: [Redmen, usedByReligiousAffiliation, Roman Catholic]
-
A.
isUsedByReligion
chosen
Indicates that something (such as an object, practice, text, or symbol) is employed or utilized within the context of a particular religion.
-
B.
usedReligionFor
Indicates that an entity employed religion as a means or tool to achieve some purpose, goal, or effect.
-
C.
religiousAffiliation
Indicates that one entity has a specified religious association, belief system, or denominational membership.
-
D.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
E.
relationshipToReligion
Indicates the nature or type of connection an entity has to a religion, such as affiliation, stance, or involvement.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 12:50 a.m.