Triple
T31910750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silesian Germans |
E814675
|
entity |
| Predicate | traditionalReligionMajority |
P2986
|
FINISHED |
| Object | 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: Catholic | Statement: [Silesian Germans, traditionalReligionMajority, Catholic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalReligionMajority Context triple: [Silesian Germans, traditionalReligionMajority, Catholic]
-
A.
majorReligionCanBe
Indicates that an entity can have a particular major religion as one of its possible primary religious affiliations.
-
B.
traditionalReligionName
Indicates that an entity has a name specifically associated with a traditional or indigenous religion.
-
C.
laterReligionDominant
Indicates that a religion adopted or followed at a later time becomes the dominant or primary religion in the relevant context or entity.
-
D.
dominantReligion
chosen
Indicates the religion that holds primary or majority status within a given group, region, or entity.
-
E.
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).
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 1, 2026, 12:01 a.m.