Triple
T28586776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devon tin trade |
E723524
|
entity |
| Predicate | taxedBy |
P25448
|
FINISHED |
| Object | English Crown |
—
|
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: English Crown | Statement: [Devon tin trade, taxedBy, English Crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxedBy Context triple: [Devon tin trade, taxedBy, English Crown]
-
A.
taxOn
chosen
Indicates that one entity imposes or applies a tax on another entity or item.
-
B.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
C.
taxBurden
Indicates the extent to which an entity is obligated to pay taxes, typically reflecting the level or share of tax liability it bears.
-
D.
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).
-
E.
taxPoint
Indicates the specific time or event at which a tax obligation is considered to arise or become chargeable for a transaction or activity.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f650faaa6481909c631878bda4d1eb |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cb1cf5481908a4fb19b531f52e2 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:18 a.m.