Triple
T7873823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Sheriff of Berkshire |
E182801
|
entity |
| Predicate | isPartlyReplacedBy |
P40785
|
FINISHED |
| Object | police forces in Berkshire |
—
|
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: police forces in Berkshire | Statement: [High Sheriff of Berkshire, isPartlyReplacedBy, police forces in Berkshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartlyReplacedBy Context triple: [High Sheriff of Berkshire, isPartlyReplacedBy, police forces in Berkshire]
-
A.
partlyReplacedBy
chosen
Indicates that one entity has been superseded or substituted in part, but not entirely, by another entity.
-
B.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
C.
mayBeReplacedBy
Indicates that one entity can potentially be substituted or superseded by another entity.
-
D.
replacedInSomeWorkflowsBy
Indicates that in certain workflows or processes, one entity is substituted or superseded by another.
-
E.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39a7f1648190980db4db1a800189 |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae928e1b88190b0620f4c4f03bc7d |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:56 p.m.