Triple
T9585645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick Temple |
E231281
|
entity |
| Predicate | termStartAsArchbishopOfCanterbury |
P26450
|
FINISHED |
| Object | 1896 |
—
|
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: 1896 | Statement: [Frederick Temple, termStartAsArchbishopOfCanterbury, 1896]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termStartAsArchbishopOfCanterbury Context triple: [Frederick Temple, termStartAsArchbishopOfCanterbury, 1896]
-
A.
startTimeAsArchbishopOfCanterbury
chosen
Indicates the date and time when an individual began serving as Archbishop of Canterbury.
-
B.
startTimeOfEpiscopate
Indicates the date and time when a person's period of serving as a bishop (episcopate) begins.
-
C.
endTimeAsArchbishopOfCanterbury
Indicates the date and time when an individual’s tenure as Archbishop of Canterbury comes to an end.
-
D.
officeStartAsArchbishopOfYork
Indicates the point in time when an individual begins serving in the role of Archbishop of York.
-
E.
beganTermAsPresidingBishopOn
Indicates the date on which an individual started their term serving in the role of Presiding Bishop.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99edc2c08190b67b40f6214d46f1 |
completed | April 1, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:06 p.m.