Triple
T19951699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic Reaction Force |
E479570
|
entity |
| Predicate | religiousAlignmentClaimed |
P45
|
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: [Catholic Reaction Force, religiousAlignmentClaimed, Protestant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousAlignmentClaimed Context triple: [Catholic Reaction Force, religiousAlignmentClaimed, Protestant]
-
A.
religiousAffiliation
chosen
Indicates that one entity has a specified religious association, belief system, or denominational membership.
-
B.
religiousClaim
Indicates that an entity asserts, expresses, or is associated with a statement or belief grounded in religion or spiritual doctrine.
-
C.
religiousAttitude
Indicates an entity’s stance, disposition, or orientation toward religion or religious beliefs.
-
D.
religiousOrientationRole
Indicates a role or position that an entity holds in relation to a particular religious orientation or affiliation.
-
E.
religiousSpectrum
Indicates a relationship that places entities along a range or continuum of religious belief, practice, or affiliation.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6c87388190a1bada3117acaf7b |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.