Triple
T2953195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Tax |
E79868
|
entity |
| Predicate | hasBandRange |
P44311
|
FINISHED |
| Object | Band A to Band H in England and Scotland |
—
|
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: Band A to Band H in England and Scotland | Statement: [Council Tax, hasBandRange, Band A to Band H in England and Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBandRange Context triple: [Council Tax, hasBandRange, Band A to Band H in England and Scotland]
-
A.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
-
B.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
C.
bandCount
Indicates the number of bands or distinct grouped units associated with a given entity.
-
D.
includesSizeRange
Indicates that one entity specifies or covers a particular range of sizes associated with another entity.
-
E.
hasFullBandwidthChannels
Indicates that the subject possesses communication channels that operate at the maximum or designated full data transmission capacity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:57 p.m.