Triple
T30726800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1995 NBA draft |
E782297
|
entity |
| Predicate | expansionTeamDrafting |
P111598
|
FINISHED |
| Object | Toronto Raptors |
—
|
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: Toronto Raptors | Statement: [1995 NBA draft, expansionTeamDrafting, Toronto Raptors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionTeamDrafting Context triple: [1995 NBA draft, expansionTeamDrafting, Toronto Raptors]
-
A.
expansionTeamIn
Indicates that a sports team entered a league or competition as an expansion team in a specified season, year, or context.
-
B.
expansionTeamWith
Indicates that one entity is an expansion team associated with, or added to, another entity such as a league, division, or organization.
-
C.
expansionDraft
chosen
Indicates that an entity was selected or involved in an expansion draft process, typically when a league adds new teams and redistributes players.
-
D.
expansionTeamNote
Indicates that there is a note or annotation specifically about an expansion team associated with the related entities.
-
E.
expansionTeamAnnouncementDate
Indicates the date on which an expansion team is officially announced.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 8:37 p.m.