Triple
T34464049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titular Archbishop of Samosata |
E884721
|
entity |
| Predicate | isGrantedTo |
P178972
|
FINISHED |
| Object | Catholic bishop |
—
|
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: Catholic bishop | Statement: [Titular Archbishop of Samosata, isGrantedTo, Catholic bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGrantedTo Context triple: [Titular Archbishop of Samosata, isGrantedTo, Catholic bishop]
-
A.
isGrantedFor
Indicates that a permission, right, or benefit has been formally given to a specific entity for a particular purpose or use.
-
B.
grantedTo
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
-
C.
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.
-
D.
isAuthorityFor
Indicates that one entity holds recognized power, control, or decision-making responsibility over another entity or domain.
-
E.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
- F. None of above. chosen
Provenance (4 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f719458378819081725f544efb1173 |
completed | May 3, 2026, 9:45 a.m. |
Created at: May 1, 2026, 2 a.m.