Triple
T31199327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonio de Castro Mayer |
E795423
|
entity |
| Predicate | appointedBishopOfCamposOn |
P67420
|
FINISHED |
| Object | 1948-01-03 |
—
|
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: 1948-01-03 | Statement: [Antonio de Castro Mayer, appointedBishopOfCamposOn, 1948-01-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedBishopOfCamposOn Context triple: [Antonio de Castro Mayer, appointedBishopOfCamposOn, 1948-01-03]
-
A.
appointedBishopOf
chosen
Indicates that a person has been officially assigned or consecrated to serve as the bishop responsible for a particular diocese or ecclesiastical jurisdiction.
-
B.
termStartAsBishopOfCampos
Indicates the time period during which an individual serves as the bishop of Campos.
-
C.
termEndAsBishopOfCampos
Indicates the time period during which an individual held and then ceased to hold the position of Bishop of Campos.
-
D.
appointedBishopBy
Indicates that one entity was formally made a bishop through the authority or decision of another entity.
-
E.
appointedBishopOfWorcester
Indicates that an entity was formally appointed to serve as the Bishop of Worcester.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 29, 2026, 9:09 p.m.