Triple
T26410388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware suburbs of Wilmington |
E663941
|
entity |
| Predicate | taxCharacteristic |
P160526
|
FINISHED |
| Object | no state sales tax in Delaware |
—
|
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: no state sales tax in Delaware | Statement: [Delaware suburbs of Wilmington, taxCharacteristic, no state sales tax in Delaware]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxCharacteristic Context triple: [Delaware suburbs of Wilmington, taxCharacteristic, no state sales tax in Delaware]
-
A.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
B.
taxFunction
Indicates the rule or calculation method used to determine the amount of tax applied to a given input (such as income, price, or transaction).
-
C.
taxDeductible
Indicates that an expense, contribution, or item is eligible to be subtracted from taxable income under applicable tax rules.
-
D.
taxOn
Indicates that one entity imposes or applies a tax on another entity or item.
-
E.
taxSchedule
Indicates the structured plan or timetable according to which taxes are calculated, applied, and/or collected.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6113143f481909c64dfc1975e3a59 |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 11:37 p.m.