Triple
T2953161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Community Charge |
E79867
|
entity |
| Predicate | successorTax |
P32861
|
FINISHED |
| Object | Council Tax based on property bands |
—
|
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: Council Tax based on property bands | Statement: [Community Charge, successorTax, Council Tax based on property bands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorTax Context triple: [Community Charge, successorTax, Council Tax based on property bands]
-
A.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
B.
successorInPractice
chosen
Indicates that one entity has taken over the role, position, or function of another in actual practice, even if not formally or officially designated as its successor.
-
C.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
-
D.
successorInHouse
Indicates that one entity directly follows another in holding a position or role within the same house or lineage.
-
E.
successorSettlement
Indicates that one settlement directly follows and replaces another as its successor.
- 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.