Triple
T18532064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA trade deadline |
E452854
|
entity |
| Predicate | postDeadlineRule |
P132032
|
FINISHED |
| Object | players can still be waived after the deadline |
—
|
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: players can still be waived after the deadline | Statement: [NBA trade deadline, postDeadlineRule, players can still be waived after the deadline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postDeadlineRule Context triple: [NBA trade deadline, postDeadlineRule, players can still be waived after the deadline]
-
A.
hasDeadline
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
B.
notificationDeadline
Indicates the time or date by which a required notification must be sent or received.
-
C.
facesDeadline
Indicates that an entity is approaching or subject to a specific due date or time limit by which a task or obligation must be completed.
-
D.
startDateRule
Indicates the rule or condition that determines when something is allowed or required to start.
-
E.
postdates
Indicates that one event or entity occurs or is established later in time than another.
- F. None of above. chosen
Provenance (4 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533fe35288190977c85ee0bb96264 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:37 a.m.