Triple
T22213527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA luxury tax |
E549014
|
entity |
| Predicate | rateIncreasesWith |
P35660
|
FINISHED |
| Object | amount above tax threshold |
—
|
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: amount above tax threshold | Statement: [NBA luxury tax, rateIncreasesWith, amount above tax threshold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rateIncreasesWith Context triple: [NBA luxury tax, rateIncreasesWith, amount above tax threshold]
-
A.
increasedRateOn
Indicates that one entity has raised the rate, fee, or charge applied to another entity.
-
B.
fareIncreasesRequire
Indicates that any increase in fare is contingent upon or must be accompanied by a specified requirement or condition.
-
C.
increasesWith
chosen
Indicates that as the value or magnitude of one entity grows, the value or magnitude of another entity correspondingly grows as well.
-
D.
increases
Indicates that one entity causes another entity’s value, level, or intensity to become larger or higher.
-
E.
rate
Indicates the numerical evaluation or assessment assigned by one entity to another based on perceived quality, performance, or value.
- 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b2d607c81909511761b5563ddee |
completed | April 28, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.