Triple
T2953156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Community Charge |
E79867
|
entity |
| Predicate | collectionAuthority |
P34545
|
FINISHED |
| Object | local authorities in Great Britain |
—
|
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: local authorities in Great Britain | Statement: [Community Charge, collectionAuthority, local authorities in Great Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionAuthority Context triple: [Community Charge, collectionAuthority, local authorities in Great Britain]
-
A.
collectionOrigin
Indicates that one entity is the source, provenance, or originating context from which a collection of items or data has been derived or assembled.
-
B.
collectionRole
Indicates the specific function, responsibility, or position an entity holds within a collection or grouped set of items.
-
C.
collectionScope
Indicates the extent, boundaries, or range over which a collection (such as a set of items, data, or resources) is defined or intended to apply.
-
D.
collectionRepository
Indicates a relationship where a repository is responsible for storing, managing, or providing access to a collection.
-
E.
authorityNamedOn
chosen
Indicates that a specific authority or authoritative entity is explicitly identified by name in relation to another entity or record.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98fe4b688190a0f68c4f80cd6f8f |
completed | March 8, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.