Triple
T26388858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA player |
E663356
|
entity |
| Predicate | competesInSeasonType |
P28245
|
FINISHED |
| Object | postseason |
—
|
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: postseason | Statement: [NBA player, competesInSeasonType, postseason]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competesInSeasonType Context triple: [NBA player, competesInSeasonType, postseason]
-
A.
playedSeasonType
chosen
Indicates that an entity participated in or was involved with a particular type of season (e.g., regular season, playoffs, preseason) within a competition or schedule.
-
B.
competesInSeasonalFormat
Indicates that an entity participates in a competition that is organized into recurring seasons or seasonal formats.
-
C.
isMultiSeasonParticipantOf
Indicates that an entity has participated in the related entity across multiple seasons or iterations.
-
D.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
-
E.
competitionSeason
Indicates that an entity is associated with a particular competitive season or edition of a 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 26, 2026, 11:24 p.m.