Triple
T12677451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish rate of income tax |
E302852
|
entity |
| Predicate | taxCodePrefix |
P3166
|
FINISHED |
| Object | S |
—
|
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: S | Statement: [Scottish rate of income tax, taxCodePrefix, S]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxCodePrefix Context triple: [Scottish rate of income tax, taxCodePrefix, S]
-
A.
taxId
Indicates that an entity is associated with a specific taxonomic identifier used to uniquely reference its position in a taxonomic classification system.
-
B.
tailCodePrefix
Indicates that one entity’s tail code begins with, or is prefixed by, the string represented by the other entity.
-
C.
taxType
chosen
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
D.
taxingJurisdiction
Indicates the authority or region that has the legal power to impose and collect taxes on a given entity or transaction.
-
E.
hasPostalCodePrefix
Indicates that a location’s postal code begins with a specified sequence of characters.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961b0d9c88190a05d6cbcb7a1642d |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:20 p.m.