Triple
T639360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | poll tax (Community Charge) |
E16697
|
entity |
| Predicate | exemptedGroup |
P4330
|
FINISHED |
| Object | certain low-income individuals |
—
|
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: certain low-income individuals | Statement: [poll tax (Community Charge), exemptedGroup, certain low-income individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exemptedGroup Context triple: [poll tax (Community Charge), exemptedGroup, certain low-income individuals]
-
A.
exemptionType
chosen
Indicates the specific category or kind of exemption that applies in a given context.
-
B.
excludes
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
-
C.
excludesRegion
Indicates that one entity explicitly omits, leaves out, or does not apply to a specified region or geographic area.
-
D.
excludesLetter
Indicates that one entity does not contain or allow the presence of a specified letter.
-
E.
notMemberOf
Indicates that an entity does not belong to, is not included in, or is not a part of a specified group, set, or collection.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a17b125481909a6ab53424954792 |
completed | March 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69a49d0629308190bcc137639567f7c2 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.