Triple
T13234748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Government Finance Act 1992 |
E315113
|
entity |
| Predicate | introducedCouncilTax |
P66045
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Local Government Finance Act 1992, introducedCouncilTax, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedCouncilTax Context triple: [Local Government Finance Act 1992, introducedCouncilTax, true]
-
A.
introducedTaxType
chosen
Indicates that an entity (such as a government or authority) has brought a particular type of tax into existence or put it into effect.
-
B.
councilStart
Indicates the point in time or event at which a council or formal meeting officially begins.
-
C.
councilContext
Indicates that an entity participates in, is associated with, or is situated within the decision-making or deliberative setting of a council.
-
D.
councilType
Indicates the specific kind or classification of a council that an entity is associated with or designated as.
-
E.
council
Indicates that an entity serves as a governing or advisory council for another entity or within a particular domain.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d36bdf8819099949b1e0e6902d3 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:22 p.m.