Triple
T29258197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 後周 |
E741761
|
entity |
| Predicate | taxReform |
P4888
|
FINISHED |
| Object | 整頓財政與賦稅制度 |
—
|
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: 整頓財政與賦稅制度 | Statement: [後周, taxReform, 整頓財政與賦稅制度]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxReform Context triple: [後周, taxReform, 整頓財政與賦稅制度]
-
A.
reform
chosen
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
B.
taxPolicyChange
Indicates a modification in governmental rules or rates governing how taxes are assessed, collected, or applied.
-
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.
proposedTaxPolicyChange
Indicates that an entity has put forward a modification or new approach to existing tax rules or structures for consideration or implementation.
-
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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f664af8ca48190bfd74d02b761a1b4 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:39 p.m.