Triple
T12455762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clifford trust doctrine |
E297653
|
entity |
| Predicate | taxConsequence |
P39307
|
FINISHED |
| Object | trust income taxed to grantor |
—
|
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: trust income taxed to grantor | Statement: [Clifford trust doctrine, taxConsequence, trust income taxed to grantor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxConsequence Context triple: [Clifford trust doctrine, taxConsequence, trust income taxed to grantor]
-
A.
effectOnTaxes
chosen
Indicates how one entity or action changes, influences, or determines the amount, structure, or treatment of taxes for another entity or situation.
-
B.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
C.
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).
-
D.
taxCase
Indicates a legal case or proceeding whose primary subject is taxation or tax-related disputes between parties.
-
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_69d6ada166c48190b902972cd2408fa3 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95151e7348190a1d4953a8b416a13 |
completed | April 10, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69d94d3c27a08190a0237200203e476d |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.