Triple
T30294227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Sheriff of Bristol |
E770470
|
entity |
| Predicate | hasChangedRole |
P67036
|
FINISHED |
| Object | now primarily ceremonial |
—
|
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: now primarily ceremonial | Statement: [High Sheriff of Bristol, hasChangedRole, now primarily ceremonial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChangedRole Context triple: [High Sheriff of Bristol, hasChangedRole, now primarily ceremonial]
-
A.
hasProposedRole
Indicates that one entity has suggested or put forward a specific role or position for another entity.
-
B.
roleReplacedOn
Indicates that one role has been substituted or taken over by another role at a specific point in time.
-
C.
changedAfter
Indicates that one entity underwent a change at a point in time that is later than the time at which another referenced entity changed.
-
D.
changedFrom
chosen
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
E.
hasPolicyChange
Indicates that a change has been made to an existing policy or set of policies affecting the related entities.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 29, 2026, 7:47 p.m.