Triple
T7525460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cook County Assessor |
E177878
|
entity |
| Predicate | governsTaxBase |
P59668
|
FINISHED |
| Object | property tax base of Cook County |
—
|
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: property tax base of Cook County | Statement: [Cook County Assessor, governsTaxBase, property tax base of Cook County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsTaxBase Context triple: [Cook County Assessor, governsTaxBase, property tax base of Cook County]
-
A.
hasPropertyTaxBase
chosen
Indicates that one entity serves as the property tax base or source from which another entity’s property tax is assessed or calculated.
-
B.
taxationMethod
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
-
C.
hasTaxPolicyResponsibility
Indicates that an entity holds authority or duty for creating, managing, or overseeing tax-related policies for another entity or jurisdiction.
-
D.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
E.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f7c7ac5c8190bbf9befdff791de0 |
completed | March 27, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:46 p.m.