Triple
T38083434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disabled Person’s Tax Credit |
E950913
|
entity |
| Predicate | calculatedBasedOn |
P71610
|
FINISHED |
| Object | earned income |
—
|
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: earned income | Statement: [Disabled Person’s Tax Credit, calculatedBasedOn, earned income]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calculatedBasedOn Context triple: [Disabled Person’s Tax Credit, calculatedBasedOn, earned income]
-
A.
calculatedOn
chosen
Indicates that a value, result, or outcome is computed based on or using the referenced entity as its input, basis, or context.
-
B.
basedOnValues
Indicates that something is determined, derived, or decided according to specified values or value-based criteria.
-
C.
calculated
Indicates that one entity has determined or computed a value, result, or outcome based on information from another entity.
-
D.
calculationBasis
Indicates the rule, method, or reference standard used as the foundation for performing a calculation in the relationship.
-
E.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.