Triple
T2953211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Tax |
E79868
|
entity |
| Predicate | billingAuthorityType |
P44313
|
FINISHED |
| Object | district council |
—
|
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: district council | Statement: [Council Tax, billingAuthorityType, district council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billingAuthorityType Context triple: [Council Tax, billingAuthorityType, district council]
-
A.
payerType
Indicates the type or category of entity responsible for making a payment in the relationship.
-
B.
issuerType
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
-
C.
signatoryType
Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
-
D.
beneficiaryType
Indicates the type or category of beneficiary that receives or is intended to receive the benefit or outcome of an action or resource.
-
E.
billType
Indicates the classification or category assigned to a bill (such as its kind, purpose, or procedural type).
- 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.