Triple
T32605502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristol customs service |
E833496
|
entity |
| Predicate | collectedTaxOn |
P25448
|
FINISHED |
| Object | imported commodities |
—
|
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: imported commodities | Statement: [Bristol customs service, collectedTaxOn, imported commodities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectedTaxOn Context triple: [Bristol customs service, collectedTaxOn, imported commodities]
-
A.
taxCollectedFrom
Indicates that a tax payment is received by one party from another as the liable payer.
-
B.
taxOn
chosen
Indicates that one entity imposes or applies a tax on another entity or item.
-
C.
taxCollectorFor
Indicates that one entity is responsible for collecting taxes on behalf of another entity, such as a government, organization, or jurisdiction.
-
D.
taxPoint
Indicates the specific time or event at which a tax obligation is considered to arise or become chargeable for a transaction or activity.
-
E.
mayNotFullyCollectTaxFor
Indicates that one party is not permitted or not able to collect the full amount of tax owed on behalf of another party.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 1:05 a.m.