Triple
T35865223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American 3 Hockey League |
E1037066
|
entity |
| Predicate | hasDraftOrTendersSystem |
P168692
|
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: [North American 3 Hockey League, hasDraftOrTendersSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDraftOrTendersSystem Context triple: [North American 3 Hockey League, hasDraftOrTendersSystem, yes]
-
A.
hasDraftOrAssignmentSystem
Indicates that an entity possesses or is associated with a system for managing drafts or assignments.
-
B.
hasDraftOrRecruitmentMethod
chosen
Indicates that there exists a specific draft system or recruitment method used to select or acquire participants or members.
-
C.
hasDraft
Indicates that one entity possesses or is associated with a preliminary or unfinished version of another entity.
-
D.
usesDraftSystem
Indicates that one entity employs or operates using a draft-based system or mechanism rather than a finalized or direct method.
-
E.
hasDraftClass
Indicates that an entity is associated with, or belongs to, a particular draft classification or draft category.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:06 p.m.