Triple
T1084669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pastor aeternus |
E24022
|
entity |
| Predicate | authorityTypeDefined |
P10788
|
FINISHED |
| Object | papal primacy |
—
|
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: papal primacy | Statement: [Pastor aeternus, authorityTypeDefined, papal primacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorityTypeDefined Context triple: [Pastor aeternus, authorityTypeDefined, papal primacy]
-
A.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
-
B.
legalAuthorityOver
Indicates that one entity has the recognized power or right to make, enforce, or adjudicate rules or decisions concerning another entity.
-
C.
designatesAuthority
Indicates that one entity formally assigns or confers decision-making power or control over something to another entity.
-
D.
hasPublicAuthorityType
chosen
Indicates that an entity possesses a specific type or category of public authority status or role.
-
E.
usesAuthorityOf
Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9608bac819085196cc0f8fbb2e7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.