Triple
T17591699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penny Hardaway |
E428463
|
entity |
| Predicate | selectedInDraft |
P81554
|
FINISHED |
| Object | 1993 NBA 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: 1993 NBA draft | Statement: [Penny Hardaway, selectedInDraft, 1993 NBA draft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectedInDraft Context triple: [Penny Hardaway, selectedInDraft, 1993 NBA draft]
-
A.
selectedAt
chosen
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
B.
selectedWith
Indicates that one entity is chosen or picked in conjunction with, or as part of a set including, another entity.
-
C.
hasDraft
Indicates that one entity possesses or is associated with a preliminary or unfinished version of another entity.
-
D.
selectedTo
Indicates that one entity has been chosen or designated from a set of candidates to perform a role, receive something, or participate in an activity in relation to another entity.
-
E.
supportsDrafts
Indicates that an entity is capable of handling, saving, or working with draft versions of items before they are finalized.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469e79dac8190953a1ce8fc015b20 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.