Triple
T7380116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Sheriff of South Yorkshire |
E170225
|
entity |
| Predicate | officeIsUnpaid |
P17781
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [High Sheriff of South Yorkshire, officeIsUnpaid, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeIsUnpaid Context triple: [High Sheriff of South Yorkshire, officeIsUnpaid, true]
-
A.
isUnpaid
chosen
Indicates that an expected payment, fee, or financial obligation has not yet been made or settled.
-
B.
officeState
Indicates the current operational or functional status of an office (e.g., open, closed, active, inactive) at a given time.
-
C.
officeContingentOn
Indicates that holding or obtaining one office, position, or role is dependent on the prior existence, status, or outcome of another specified office or condition.
-
D.
officeSuspendedUnder
Indicates that an individual’s official position or duties are temporarily halted under the authority or jurisdiction of a specified entity or rule.
-
E.
officeMayBeVacant
Indicates that an office has the possibility of being unoccupied or without an active occupant.
- 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1c61484819087874d4e7f9fd791 |
completed | March 27, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:08 p.m.