Triple
T7979055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Sheriff of Devon |
E185518
|
entity |
| Predicate | officeHoldersAssumeOfficeOn |
P1814
|
FINISHED |
| Object | March |
—
|
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: March | Statement: [High Sheriff of Devon, officeHoldersAssumeOfficeOn, March]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHoldersAssumeOfficeOn Context triple: [High Sheriff of Devon, officeHoldersAssumeOfficeOn, March]
-
A.
lastOfficeHolderStartDate
Indicates the date on which the most recent person to hold a particular office or position began their term.
-
B.
termOfOfficeInaugurated
Indicates the event or date on which an individual officially begins their term of office through an inauguration.
-
C.
currentSpeakerAssumedOffice
Indicates that the person who is currently serving as speaker has taken up or begun holding a particular office or position.
-
D.
officeHolderStartTime
chosen
Indicates the date and time at which an individual begins holding a particular office or position.
-
E.
inauguralHolderStartDate
Indicates the date on which the first person or entity to hold a position, title, or role officially began their tenure.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c261904819086910898071f3629 |
completed | March 31, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:14 p.m.