Triple
T28685375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Sheriff of Sussex |
E729116
|
entity |
| Predicate | officeHoldersNumberPerTerm |
P195040
|
FINISHED |
| Object | one |
—
|
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: one | Statement: [High Sheriff of Sussex, officeHoldersNumberPerTerm, one]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHoldersNumberPerTerm Context triple: [High Sheriff of Sussex, officeHoldersNumberPerTerm, one]
-
A.
officeHoldersNumber
Indicates the number of individuals who hold a particular office or position.
-
B.
firstOfficeHoldersCount
Indicates the number of individuals who initially held a particular office or position.
-
C.
officeHolderCountIncludes
Indicates that a specified count or total explicitly includes the number of individuals holding a particular office or position.
-
D.
numberOfTermInOffice
Indicates the specific ordinal count of how many terms an entity has served in a particular office or position.
-
E.
officeHoldersNumbered
Indicates that a specific office or position has its holders identified and distinguished by assigned numbers (e.g., first holder, second holder, etc.).
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
| PDg | Predicate description generation | batch_69fd9fef7aac819089cc88dd3d00296d |
completed | May 8, 2026, 8:33 a.m. |
Created at: April 28, 2026, 5:31 a.m.