Triple
T23123180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pay As You Earn |
E576954
|
entity |
| Predicate | calculationUses |
P4746
|
FINISHED |
| Object | adjusted gross 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: adjusted gross income | Statement: [Pay As You Earn, calculationUses, adjusted gross income]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calculationUses Context triple: [Pay As You Earn, calculationUses, adjusted gross income]
-
A.
formulaUsed
Indicates that a particular formula is employed or applied in performing a calculation, derivation, or reasoning step.
-
B.
calculationType
Indicates the specific method, formula, or approach used to perform a calculation in the described relationship.
-
C.
mathematicallyUses
chosen
Indicates that one entity employs or applies another entity within a mathematical context, such as in a formula, proof, computation, or theoretical framework.
-
D.
calculated
Indicates that one entity has determined or computed a value, result, or outcome based on information from another entity.
-
E.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e517a0481909829a73fdf255d1c |
completed | April 29, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:59 p.m.