Triple
T200024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA champion |
E4082
|
entity |
| Predicate | playoffStructureIncludes |
P3749
|
FINISHED |
| Object | first round |
—
|
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: first round | Statement: [NBA champion, playoffStructureIncludes, first round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffStructureIncludes Context triple: [NBA champion, playoffStructureIncludes, first round]
-
A.
playoffStructure
chosen
Indicates how a competition’s postseason phase is organized, including the format, seeding, and progression of teams or players through playoff rounds.
-
B.
playoffName
Indicates the designated name or title assigned to a specific playoff series, round, or event within a competition.
-
C.
playoffAppearances
Indicates the number of times an entity (such as a team or player) has qualified for and participated in postseason playoff competition.
-
D.
numberOfPlayoffTeams
Indicates the total count of teams that qualify for or participate in the playoffs within a given league or season.
-
E.
postseasonType
Indicates the specific kind of postseason competition or phase associated with an event or team.
- 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25bcc6dc88190b8c24b485588dfe4 |
completed | Feb. 28, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69a25b4886b48190b46fd2244648a098 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.