Triple
T960655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reformed churches |
E20728
|
entity |
| Predicate | regardsAsUltimateAuthority |
P13836
|
FINISHED |
| Object | Holy Scripture |
—
|
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: Holy Scripture | Statement: [Reformed churches, regardsAsUltimateAuthority, Holy Scripture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regardsAsUltimateAuthority Context triple: [Reformed churches, regardsAsUltimateAuthority, Holy Scripture]
-
A.
usesAuthorityOf
Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
-
B.
designatesAuthority
Indicates that one entity formally assigns or confers decision-making power or control over something to another entity.
-
C.
legalAuthorityOver
Indicates that one entity has the recognized power or right to make, enforce, or adjudicate rules or decisions concerning another entity.
-
D.
recognizesAuthority
chosen
Indicates that one entity accepts, acknowledges, or submits to the power, control, or legitimate decision-making role of another entity.
-
E.
uniformAuthority
Indicates that an authority or governing body applies rules, standards, or control consistently and uniformly across all relevant entities or situations.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b4144c208190980936347a95e233 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a2e23c8190b932fe88b02f995d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.