Triple
T2817824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Sweden |
E54332
|
entity |
| Predicate | becameStateChurch |
P30493
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Church of Sweden, becameStateChurch, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameStateChurch Context triple: [Church of Sweden, becameStateChurch, 16th century]
-
A.
hadNationalChurch
Indicates that a country or region recognized a particular church as its official or primary national religious institution.
-
B.
establishedChurch
chosen
Indicates that a particular church is officially recognized and supported by the state as its formal or primary religious institution.
-
C.
isStateChurch
Indicates that a church is officially recognized and established as the state’s or government’s official religion.
-
D.
isEstablishedChurchIn
Indicates that a church is officially recognized and established as the state or national church within a specified jurisdiction or territory.
-
E.
establishedAsDiocese
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of a diocese.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abdf15b7288190a03d1193cc0544a6 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd08f2f481908c3da8a9c7a00552 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.