Triple
T35304036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Hallam |
E1019583
|
entity |
| Predicate | Gerald Moverley_startOfOffice |
P182717
|
FINISHED |
| Object | 1980-05-30 |
—
|
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: 1980-05-30 | Statement: [Roman Catholic Diocese of Hallam, Gerald Moverley_startOfOffice, 1980-05-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Gerald Moverley_startOfOffice Context triple: [Roman Catholic Diocese of Hallam, Gerald Moverley_startOfOffice, 1980-05-30]
-
A.
Roger MullinTermStart
Indicates the date or time period when Roger Mullin began his term in an official role or position.
-
B.
thirdOfficeHolderStartDate
Indicates the date on which the third person to hold a particular office or position began their term.
-
C.
lastOfficeHolderStartDate
Indicates the date on which the most recent person to hold a particular office or position began their term.
-
D.
significantOfficeHolderStartTime
Indicates the date and time at which an entity begins holding a significant office or position.
-
E.
fourthOfficeHolderStartDate
Indicates the date on which the fourth person to hold a particular office or position began their term.
- F. None of above. chosen
Provenance (4 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904d95b48190b98dca59dbb592d8 |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:03 p.m.