Triple
T5900924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Rebels |
E131221
|
entity |
| Predicate | playoffAppearanceSeason |
P65469
|
FINISHED |
| Object | 1946–47 BAA season |
—
|
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: 1946–47 BAA season | Statement: [Cleveland Rebels, playoffAppearanceSeason, 1946–47 BAA season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffAppearanceSeason Context triple: [Cleveland Rebels, playoffAppearanceSeason, 1946–47 BAA season]
-
A.
playoffAppearances
Indicates the number of times an entity (such as a team or player) has qualified for and participated in postseason playoff competition.
-
B.
madePlayoffsInSeason
chosen
Indicates that a team qualified for and participated in the playoffs during a specified season.
-
C.
playoffParticipation
Indicates that an entity takes part in a postseason playoff competition within a given league or tournament.
-
D.
hadPlayoffBerthsEachSeason
Indicates that the subject team qualified for the playoffs in every season within the specified time span.
-
E.
postseasonGamesPlayed
Indicates the number of games an entity has participated in during postseason or playoff competition.
- 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0334dc8248190b7394dcece362d52 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.