Triple
T26200714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSL |
E655222
|
entity |
| Predicate | hasPlayerDraft |
P1035
|
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: [PSL, hasPlayerDraft, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayerDraft Context triple: [PSL, hasPlayerDraft, yes]
-
A.
hasDraftedPlayersTo
Indicates that one entity has selected or drafted players to join or belong to another entity, such as a team, league, or organization.
-
B.
draftedIn
chosen
Indicates that one entity was selected or recruited into another entity (such as a team, organization, or military service) through a formal draft process.
-
C.
draftedFor
Indicates that one entity has been selected or assigned, typically through a draft process, to serve, play, or work for another entity.
-
D.
draftedDuring
Indicates that an entity was formally selected or conscripted (e.g., into military service or a professional league) within the time span of a specified event or period.
-
E.
draftedAt
Indicates that an entity was selected or chosen by another entity at a specific draft event or position.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 26, 2026, 8:48 p.m.