Triple
T38021257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry, King of Portugal |
E948636
|
entity |
| Predicate | papalAppointment |
P63957
|
FINISHED |
| Object | created cardinal by Pope Paul III |
—
|
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: created cardinal by Pope Paul III | Statement: [Henry, King of Portugal, papalAppointment, created cardinal by Pope Paul III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: papalAppointment Context triple: [Henry, King of Portugal, papalAppointment, created cardinal by Pope Paul III]
-
A.
papalDesignation
chosen
Indicates a formal status, title, or role that has been officially conferred by the Pope or the papal authority.
-
B.
electedPope
Indicates that one person or body has chosen or appointed another individual to serve as Pope.
-
C.
electedPopeAt
Indicates that one entity was chosen and formally installed as Pope at a specific time or event associated with another entity.
-
D.
electedAsPopeBy
Indicates that one party became Pope through the formal selection or voting decision made by another party or group.
-
E.
papalElection
Indicates the process or event in which a new pope is chosen and formally elected to the papal office.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.