Triple
T3936865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Professional Hockey League |
E90932
|
entity |
| Predicate | payingPlayers |
P52641
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ontario Professional Hockey League, payingPlayers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payingPlayers Context triple: [Ontario Professional Hockey League, payingPlayers, yes]
-
A.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
B.
pays
Indicates that one entity gives money or another form of compensation to another entity, typically in exchange for goods, services, or to settle a debt.
-
C.
revenuePaidTo
Indicates that a specified amount of revenue is paid or transferred from one entity to another as a recipient.
-
D.
winnerReceives
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
-
E.
managedPlayers
Indicates that one entity has managerial responsibility or authority over the players represented by the other entity.
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedceab608190934293d432f14476 |
completed | March 9, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeed3260cc8190bf294bdab507b1f9 |
completed | March 9, 2026, 3:54 p.m. |
Created at: March 9, 2026, 3:23 p.m.