Triple
T13068914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Hockey League |
E329401
|
entity |
| Predicate | hasSalaryBudgetConstraints |
P2676
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Austrian Hockey League, hasSalaryBudgetConstraints, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSalaryBudgetConstraints Context triple: [Austrian Hockey League, hasSalaryBudgetConstraints, true]
-
A.
usesSalaryBudgets
Indicates that one entity allocates or manages financial resources for compensation based on predefined salary budgets associated with another entity.
-
B.
hasBudgetFor
Indicates that an entity possesses sufficient allocated financial resources to support, fund, or carry out another specified entity, activity, or purpose.
-
C.
hasCapitalBudgetFor
Indicates that an entity allocates or designates financial resources specifically for capital expenditures related to another entity or purpose.
-
D.
usesSalaryCap
chosen
Indicates that an entity applies or operates under a salary cap constraint when managing compensation or payroll.
-
E.
budgetLevel
Indicates the relative amount of financial resources allocated or available for something, typically categorized by level (e.g., low, medium, high).
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980ec8ba48190baf52c7823482680 |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9 p.m.