Triple
T36176941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contra Costa County unincorporated area |
E1046597
|
entity |
| Predicate | subjectToTaxationBy |
P79121
|
FINISHED |
| Object | Contra Costa County |
—
|
NE NERFINISHED |
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: Contra Costa County | Statement: [Contra Costa County unincorporated area, subjectToTaxationBy, Contra Costa County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToTaxationBy Context triple: [Contra Costa County unincorporated area, subjectToTaxationBy, Contra Costa County]
-
A.
subjectToWithholdingTax
Indicates that payments or income associated with an entity are required to have a portion withheld and remitted as tax before the recipient receives the net amount.
-
B.
positionOnTaxation
Indicates a stance or viewpoint an entity holds regarding tax policies, levels, or structures.
-
C.
taxingJurisdiction
chosen
Indicates the authority or region that has the legal power to impose and collect taxes on a given entity or transaction.
-
D.
taxationMethod
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
-
E.
taxOn
Indicates that one entity imposes or applies a tax on another entity or item.
- 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 3, 2026, 4:08 p.m.