Triple
T24976126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Augustus Selwyn |
E625025
|
entity |
| Predicate | officeStart(Bishop of New Zealand) |
P73919
|
FINISHED |
| Object | 1841 |
—
|
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: 1841 | Statement: [George Augustus Selwyn, officeStart(Bishop of New Zealand), 1841]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeStart(Bishop of New Zealand) Context triple: [George Augustus Selwyn, officeStart(Bishop of New Zealand), 1841]
-
A.
startTimeOfPositionHeld:Bishop of New Zealand
chosen
Indicates the date and time when an individual began holding the position of Bishop of New Zealand.
-
B.
startTime (Archbishop of Wales)
Indicates the point in time at which someone begins serving as Archbishop of Wales.
-
C.
officeStartAsArchbishopOfYork
Indicates the point in time when an individual begins serving in the role of Archbishop of York.
-
D.
firstBishop
Indicates that one entity is the first bishop (earliest in time or rank) associated with or holding episcopal authority over another entity.
-
E.
startTime (Bishop of Durham)
Indicates the point in time at which someone began serving as Bishop of Durham.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 18, 2026, 6:01 a.m.