Triple
T6880523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Augustus Selwyn |
E158780
|
entity |
| Predicate | ordinationYear:priest |
P13557
|
FINISHED |
| Object | 1834 |
—
|
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: 1834 | Statement: [George Augustus Selwyn, ordinationYear:priest, 1834]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordinationYear:priest Context triple: [George Augustus Selwyn, ordinationYear:priest, 1834]
-
A.
ordinationAsPriestYear
chosen
Indicates the year in which an individual was formally ordained as a priest.
-
B.
priests
Indicates that the subject serves in a religious or spiritual officiating role, typically performing sacred rituals or duties for a faith community.
-
C.
wasOrdainedAs
Indicates that an entity was formally appointed or consecrated into an official religious or ceremonial role.
-
D.
ordainedBy
Indicates that an entity has been formally appointed, consecrated, or invested with authority by another entity.
-
E.
ecclesiasticalRole
Indicates that one entity holds or is assigned a specific religious or church-related office, function, or position in relation to 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_69c688342f6c8190ad7eea6ba262db99 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8e798c08190b1f494a2c1445514 |
completed | March 27, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:23 p.m.