Triple
T33946080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLR |
E870292
|
entity |
| Predicate | hasCollegiateDraft |
P206744
|
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: [MLR, hasCollegiateDraft, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollegiateDraft Context triple: [MLR, hasCollegiateDraft, yes]
-
A.
hasJuniorDraftEligibility
Indicates that an individual meets the criteria to be eligible for selection in a junior-level draft.
-
B.
hasJuniorDraftRights
Indicates that one party holds the exclusive rights to draft or sign a junior-level player associated with another entity (such as a team or league).
-
C.
madeCollegiateDebut
Indicates that an individual participated in their first official competition or appearance at the collegiate level.
-
D.
draftedWith
Indicates that one entity was created, written, or prepared using the assistance, tools, or content of another entity.
-
E.
draftedInto
Indicates that an entity is formally selected or conscripted to join and serve in a particular organization, group, or role, typically without initiating the choice themselves.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.