Triple
T1578676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1995–96 NBA season |
E33711
|
entity |
| Predicate | notableTeamRecord |
P16995
|
FINISHED |
| Object | Chicago Bulls 72–10 regular-season record |
—
|
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: Chicago Bulls 72–10 regular-season record | Statement: [1995–96 NBA season, notableTeamRecord, Chicago Bulls 72–10 regular-season record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTeamRecord Context triple: [1995–96 NBA season, notableTeamRecord, Chicago Bulls 72–10 regular-season record]
-
A.
notableTeamSeason
Indicates that a particular sports season is especially significant or noteworthy in the history of a given team.
-
B.
notableEventTeam
Indicates a team that is significantly associated with, or played a key role in, a particular notable event.
-
C.
notableRivalTeam
Indicates that one team is recognized as a significant or well-known rival of another team.
-
D.
notableStatistic
chosen
Indicates that a particular statistic is especially significant or noteworthy in relation to the subject.
-
E.
notablePlayerTeam1
Indicates that the referenced player is a notable or prominent member of the first team in a given context or matchup.
- 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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abacfb1144819080c5687175aba1e1 |
completed | March 7, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69aa61b0f5bc8190b1dc272990a59c13 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:27 p.m.