Triple
T2456453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Norway |
E54432
|
entity |
| Predicate | usesScriptureLanguage |
P25852
|
FINISHED |
| Object | Norwegian Bible translations |
—
|
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: Norwegian Bible translations | Statement: [Church of Norway, usesScriptureLanguage, Norwegian Bible translations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesScriptureLanguage Context triple: [Church of Norway, usesScriptureLanguage, Norwegian Bible translations]
-
A.
hasLanguageOfScripture
Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
-
B.
usedScriptureTranslation
Indicates that one entity employed or relied on a particular translation of scripture in its actions, works, or communications.
-
C.
typicalLanguageOfReadings
chosen
Indicates the language that is most commonly used for readings or interpretations associated with a given entity.
-
D.
recognizesScripturesFrom
Indicates that one entity acknowledges or accepts certain scriptures as authoritative or valid based on another entity as their source or origin.
-
E.
scriptureTypeTranslated
Indicates that a scripture or sacred text has been translated into a particular type, version, or format.
- 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd49c5aa081909ab4f726a458b77f |
completed | March 7, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69abd0b199488190aa381b36593ae1ac |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.