Triple
T28700445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL player |
E729535
|
entity |
| Predicate | collectiveBargainingAgreementWith |
P9252
|
FINISHED |
| Object | NHL Players’ Association |
—
|
NE NERFINISHED |
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: NHL Players’ Association | Statement: [NHL player, collectiveBargainingAgreementWith, NHL Players’ Association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectiveBargainingAgreementWith Context triple: [NHL player, collectiveBargainingAgreementWith, NHL Players’ Association]
-
A.
formedByAgreementWith
Indicates that something comes into existence or is established as a direct result of a formal agreement between parties.
-
B.
limitsCollectiveBargainingTo
Indicates that one party imposes restrictions on the scope or exercise of collective bargaining rights available to another party or group.
-
C.
basedOnAgreementWith
chosen
Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
-
D.
implementsAgreementWith
Indicates that one party carries out or fulfills the terms of an agreement made with another party.
-
E.
aimOfAgreement
Indicates the intended purpose or objective that an agreement is designed to achieve.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 5:42 a.m.