Triple
T27688240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mega Basket |
E698088
|
entity |
| Predicate | hasNBAAlumni |
P114946
|
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: [Mega Basket, hasNBAAlumni, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNBAAlumni Context triple: [Mega Basket, hasNBAAlumni, yes]
-
A.
notableAlumnusInNBA
Indicates that a person is a distinguished former student of an institution who has gone on to play in the NBA.
-
B.
hallOfFameAlumnus
Indicates that an individual is recognized as a Hall of Fame member associated with a particular institution, organization, or group.
-
C.
allowedNBAPlayersFrom
Indicates that certain NBA players are permitted or eligible to come from a specified source, such as a team, region, or category.
-
D.
hasNBAFranchiseHistoryFrom
Indicates that an entity has a history of operating an NBA franchise originating from a specified location or organization.
-
E.
hasNotableSportAlumnus
chosen
Indicates that an institution or organization has at least one alumnus who is notable for achievements in sports.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63574d2388190839cd1061e3c9074 |
completed | May 2, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:50 p.m.