Triple
T21540323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Hockey League |
E531465
|
entity |
| Predicate | playerDraftType |
P72111
|
FINISHED |
| Object | junior ice hockey draft |
—
|
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: junior ice hockey draft | Statement: [Ontario Hockey League, playerDraftType, junior ice hockey draft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerDraftType Context triple: [Ontario Hockey League, playerDraftType, junior ice hockey draft]
-
A.
ドラフト種別
chosen
Indicates the type or category of a draft in relation to how it was created, selected, or classified.
-
B.
draftOverallPickType
Indicates the type or category of an entity’s selection position in an overall draft order.
-
C.
ABA draftPick
Indicates that an entity was selected as a draft pick by an ABA team in a particular draft event.
-
D.
draftedFor
Indicates that one entity has been selected or assigned, typically through a draft process, to serve, play, or work for another entity.
-
E.
ABA draftRound
Indicates the specific round in which a player was selected during an ABA draft.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d119e0c8190a207c0e8ae328a95 |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:28 p.m.