Triple
T27054154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996 NBA Draft |
E684853
|
entity |
| Predicate | fourthOverallPick |
P40299
|
FINISHED |
| Object | Stephon Marbury |
—
|
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: Stephon Marbury | Statement: [1996 NBA Draft, fourthOverallPick, Stephon Marbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fourthOverallPick Context triple: [1996 NBA Draft, fourthOverallPick, Stephon Marbury]
-
A.
overallDraftPickNumber
chosen
Indicates the specific overall position at which an entity (such as a player) is selected in a draft relative to all other selections.
-
B.
NFLDraftPickNumber
Indicates the specific overall selection position at which an individual was chosen in an NFL Draft.
-
C.
draftedUnder
Indicates that one entity was formally selected or conscripted into a role, position, or service according to the authority, rules, or jurisdiction of another entity.
-
D.
fourthPlace
Indicates that an entity holds the fourth position or rank in an ordered sequence, competition, or hierarchy.
-
E.
ABA draftPick
Indicates that an entity was selected as a draft pick by an ABA team in a particular draft event.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 8:16 a.m.