Triple
T8637789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Sheriff of Durham |
E204565
|
entity |
| Predicate | appointmentFrequency |
P84371
|
FINISHED |
| Object | annually |
—
|
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: annually | Statement: [High Sheriff of Durham, appointmentFrequency, annually]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointmentFrequency Context triple: [High Sheriff of Durham, appointmentFrequency, annually]
-
A.
meetingFrequency
Indicates how often a meeting or recurring gathering takes place over a given period.
-
B.
serviceFrequencyType
Indicates how often a service occurs or is scheduled within a given time period.
-
C.
serviceFrequencyContext
Indicates the contextual conditions or circumstances under which a service’s frequency is defined, applied, or interpreted.
-
D.
appointmentTerm
Indicates the duration or specific period for which an appointment, position, or role is held.
-
E.
meetingPeriod
Indicates the time span or duration during which a meeting takes place.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc47944d1c819081f448f14d04bf9d |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc479284a8819099b0b0d879af3372 |
completed | March 31, 2026, 10:15 p.m. |
Created at: March 30, 2026, 6:28 p.m.