Triple
T13234805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anti Poll Tax Federation |
E315114
|
entity |
| Predicate | opposedTaxType |
P108647
|
FINISHED |
| Object | local government tax |
—
|
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 government tax | Statement: [Anti Poll Tax Federation, opposedTaxType, local government tax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedTaxType Context triple: [Anti Poll Tax Federation, opposedTaxType, local government tax]
-
A.
opposedLawType
Indicates that one law is opposed to, or in conflict with, another law of a specified type.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
D.
opposedConversionOf
Indicates that one entity actively resisted, objected to, or worked against the process of converting or changing another entity.
-
E.
typeOfOpposition
Indicates a relationship where one entity stands in opposition or contrast to another, such as being a rival, adversary, or countering force.
- 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_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. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:22 p.m.