Triple
T33212938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA D-League playoffs |
E850207
|
entity |
| Predicate | relationToNBA |
P162814
|
FINISHED |
| Object | developmental system for NBA teams |
—
|
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: developmental system for NBA teams | Statement: [NBA D-League playoffs, relationToNBA, developmental system for NBA teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToNBA Context triple: [NBA D-League playoffs, relationToNBA, developmental system for NBA teams]
-
A.
relationshipToNFL
Indicates the nature or type of connection an entity has to the National Football League (NFL), such as affiliation, role, or involvement.
-
B.
equivalentInNBA
Indicates that two entities correspond to each other as equivalent counterparts within the context of the NBA.
-
C.
isFromBasketballFamily
Indicates that an individual comes from a family with a strong involvement or background in basketball.
-
D.
NBAPlayerID
Indicates that the subject is identified as an NBA player by a specific unique identifier.
-
E.
leagueLevelRelativeToNBA
chosen
Indicates the comparative competitive level or tier of a basketball league in relation to the NBA.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:30 a.m.