Triple
T25601208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladika |
E641791
|
entity |
| Predicate | combinesAuthority |
P106993
|
FINISHED |
| Object | spiritual authority |
—
|
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: spiritual authority | Statement: [Vladika, combinesAuthority, spiritual authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinesAuthority Context triple: [Vladika, combinesAuthority, spiritual authority]
-
A.
authorityConsolidation
Indicates the process by which decision-making power and control become increasingly concentrated in a single actor, group, or institution, reducing the influence of others.
-
B.
jointAuthorityOf
chosen
Indicates that two or more entities share formal power or control over a decision, resource, or domain.
-
C.
uniformAuthority
Indicates that an authority or governing body applies rules, standards, or control consistently and uniformly across all relevant entities or situations.
-
D.
usesAuthorityOf
Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
-
E.
includesAuthority
Indicates that one entity’s scope, rights, or powers encompass and subsume the authority held by another entity.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a724788190a5ae08017001c146 |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:31 p.m.