Triple
T36476879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mackie Samoskevich |
E898691
|
entity |
| Predicate | prospectLeague |
P185760
|
FINISHED |
| Object | NHL |
—
|
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 | Statement: [Mackie Samoskevich, prospectLeague, NHL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prospectLeague Context triple: [Mackie Samoskevich, prospectLeague, NHL]
-
A.
professionalLeaguePioneer
Indicates that an entity played a pioneering or foundational role in the establishment or early development of a professional sports league.
-
B.
stateLeague
Indicates that a sports team or club competes in, or is affiliated with, a particular state-level league or competition.
-
C.
includesProfessionalLeagues
Indicates that an entity contains or encompasses one or more professional sports leagues within its scope or structure.
-
D.
eligibleLeague
Indicates that an entity (such as a team or player) is qualified or permitted to participate in a particular league.
-
E.
employerLeague
Indicates that an organization or entity serves as the employing league or governing competition body for another entity (such as a team or participant).
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:10 p.m.