Triple
T33787167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020–21 NBA season |
E865823
|
entity |
| Predicate | playInTournamentSeedingRange |
P25483
|
FINISHED |
| Object | 7–10 |
—
|
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: 7–10 | Statement: [2020–21 NBA season, playInTournamentSeedingRange, 7–10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playInTournamentSeedingRange Context triple: [2020–21 NBA season, playInTournamentSeedingRange, 7–10]
-
A.
overallTournamentSeedCount
Indicates the assigned seed number or ranking position of an entity within the overall tournament field.
-
B.
playoffSeed
Indicates the ranking or position a team or player holds in a playoff bracket based on their performance or qualification criteria.
-
C.
playInTournamentIntroduced
Indicates that an entity participates as a player in a specific tournament that has been newly introduced or added.
-
D.
championSeed
Indicates that an entity is designated as the top or primary seed (expected winner) in a competitive event or tournament.
-
E.
eligibleSeedsPerConference
chosen
Indicates the specific tournament seed positions within each conference that qualify as eligible under the defined rules or criteria.
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:45 a.m.