Triple
T1137998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Laud |
E23182
|
entity |
| Predicate | appointedArchbishopOfCanterbury |
P3360
|
FINISHED |
| Object | 1633 |
—
|
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: 1633 | Statement: [William Laud, appointedArchbishopOfCanterbury, 1633]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedArchbishopOfCanterbury Context triple: [William Laud, appointedArchbishopOfCanterbury, 1633]
-
A.
archbishopOf
chosen
Indicates that a person holds the ecclesiastical office of archbishop in relation to a specific diocese, region, or church jurisdiction.
-
B.
currentSupremeGovernor
Indicates that one entity is the person who currently holds the position of supreme governor (highest governing authority) over another entity.
-
C.
episcopalSeeOf
Indicates that one entity serves as the episcopal see (the official seat or jurisdictional center) of a bishop or similar ecclesiastical authority for another entity.
-
D.
currentArchbishopStartYear
Indicates the calendar year in which the current archbishop began serving in that role.
-
E.
hasNotableArchbishop
Indicates that an entity has or has had a particularly distinguished or prominent archbishop associated with it.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4b52d48190bec2e7ad1cc8efc0 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.