Triple
T34202439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Archbishop |
E877423
|
entity |
| Predicate | receivesPalliumFrom |
P128279
|
FINISHED |
| Object | Pope |
—
|
NE NERFINISHED |
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: Pope | Statement: [Metropolitan Archbishop, receivesPalliumFrom, Pope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesPalliumFrom Context triple: [Metropolitan Archbishop, receivesPalliumFrom, Pope]
-
A.
receivedPalliumFrom
chosen
Indicates that one ecclesiastical figure has been formally granted the pallium by another, typically signifying the conferral of metropolitan authority or jurisdiction.
-
B.
holdsPallium
Indicates that one entity ceremonially carries or possesses the pallium in relation to another entity.
-
C.
receivesLivingFrom
Indicates that one entity obtains or is given a living organism or life-sustaining resource from another entity.
-
D.
receivesModulatoryInputFrom
Indicates that one entity’s activity is influenced or regulated by signals originating from another entity.
-
E.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:55 a.m.