Triple
T214835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL Entry Draft |
E4795
|
entity |
| Predicate | playerRightsConferred |
P168
|
FINISHED |
| Object | exclusive NHL signing rights |
—
|
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: exclusive NHL signing rights | Statement: [NHL Entry Draft, playerRightsConferred, exclusive NHL signing rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerRightsConferred Context triple: [NHL Entry Draft, playerRightsConferred, exclusive NHL signing rights]
-
A.
styleGranted
Indicates that a particular style, manner, or mode of expression has been conferred or authorized for use by one entity to another.
-
B.
grantedPower
Indicates that one entity has conferred authority, control, or a specific capability to another entity.
-
C.
grantedTo
chosen
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
-
D.
mediaRights
Indicates that one entity holds legal permission or authority to use, distribute, or control the use of another entity’s media content.
-
E.
hasBroadcastRightsHolder
Indicates that one entity holds the legal rights to broadcast content owned or controlled by another entity.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b52190481908f299d26122bafd2 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.