Triple
T17703813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of the Rio Grande |
E441377
|
entity |
| Predicate | mayOrdain |
P39382
|
FINISHED |
| Object | deacons |
—
|
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: deacons | Statement: [Bishop of the Rio Grande, mayOrdain, deacons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayOrdain Context triple: [Bishop of the Rio Grande, mayOrdain, deacons]
-
A.
ordains
Indicates that one entity formally appoints or invests another with authority, office, or a religious role through an official or ceremonial act.
-
B.
allowedOrdinationOf
chosen
Indicates that one entity permits or authorizes the formal religious ordination of another entity.
-
C.
ordainedFor
Indicates that one entity has been formally appointed or consecrated to serve, function, or act on behalf of another entity or purpose.
-
D.
ordainedIn
Indicates that an individual was formally appointed or consecrated to a religious office or role at a specific place or within a particular institution.
-
E.
wasOrdainedAs
Indicates that an entity was formally appointed or consecrated into an official religious or ceremonial role.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47296770c8190b6b172fb647da564 |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:05 a.m.