Triple
T69111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Hockey League |
E1381
|
entity |
| Predicate | introducedSalaryCapSeason |
P3765
|
FINISHED |
| Object | 2005-2006 |
—
|
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: 2005-2006 | Statement: [National Hockey League, introducedSalaryCapSeason, 2005-2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedSalaryCapSeason Context triple: [National Hockey League, introducedSalaryCapSeason, 2005-2006]
-
A.
usesSalaryCap
Indicates that an entity applies or operates under a salary cap constraint when managing compensation or payroll.
-
B.
managerDebutYear
Indicates the year in which an individual first began their role as a manager.
-
C.
hasDesignatedPlayerRule
Indicates that a sports league or competition uses a designated player rule allowing certain players to be treated differently for roster or salary purposes.
-
D.
designatedHitterRuleLeagueWideSince
Indicates that the designated hitter rule has been in effect across an entire league starting from a specified time.
-
E.
competitionSeason
Indicates that an entity is associated with a particular competitive season or edition of a competition.
- F. None of above. chosen
Provenance (4 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24ea8cfd081908a26edad2473dde3 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a24fcf5a88819088c5fa4c08476358 |
completed | Feb. 28, 2026, 2:15 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.